Communicating with and controlling load control systems

ABSTRACT

Systems and methods are disclosed for communicating via a communications network with a load control system of a respective user environment, receiving information on the load control system via the communications network, displaying graphical user interfaces based on the received information, and controlling and configuring the load control system via graphical user interfaces by communicating via the communications network messages the load control system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/726,755, filed Sep. 4, 2018, and the benefit of U.S.Provisional Patent Application No. 62/789,412, filed Jan. 7, 2019, eachof which is hereby incorporated by reference herein in its entirety.

BACKGROUND

A user environment, such as a residence, an office building, or a hotelfor example, may be configured to include various types of load controlsystems. For example, a lighting control system may be used to controlthe lighting loads in the user environment. A motorized window treatmentcontrol system may be used to control the natural light provided to theuser environment. A heating, ventilating, and air conditioning (HVAC)system may be used to control the temperature in the user environment.

SUMMARY

It may be desirable to communicate with and control load control systemsfrom a network device.

As on example, an apparatus may include a display screen, acommunications circuit, and at least one processor, and may furtherinclude at least one tangible memory device communicatively coupled tothe at least one processor. The at least one tangible memory device mayhave software instructions stored thereon that when executed by the atleast one processor may direct the at least one processor to receive viathe communications circuit from a communications network informationcommunicated by a controller. The controller may be configured tocommunicate with a lighting control device. The lighting control devicemay be configured to control a lighting load. The lighting load mayinclude a plurality of light emitting diodes (LEDs) including a reddiode, a green diode, and a blue diode and may be configured to produceany of a plurality of different colors through the plurality of LEDs.The information may include an indication of a color the lighting loadis configured to presently produce. The software instructions, whenexecuted by the at least one processor, may further direct the at leastone processor to display on the display screen a graphical userinterface that includes an on-off actuator to turn the lighting load onand off, a dimming actuator to change an intensity of the lighting load,a warm-cool actuator to configure the lighting load to produce a coloron a black body curve, and a full-color actuator to configure thelighting load to produce a color within a color gamut formed by theplurality LEDs that make up the lighting load. The softwareinstructions, when executed by the at least one processor, may furtherdirect the at least one processor to display with the on-off actuator inthe graphical user interface an indicator that indicates the color thelighting load is configured to presently produce.

The above advantages and features are of representative embodimentsonly. They are not to be considered limitations. Additional features andadvantages of embodiments will become apparent in the followingdescription, from the drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The patent or application file contains at least one drawing executed incolor. Copies of this patent or patent application publication withcolor drawing(s) will be provided by the Office upon request and paymentof the necessary fee.

FIG. 1 is a system diagram that illustrates an example load controlsystem that includes control-devices.

FIG. 2 is a system diagram that illustrates a system for communicatingwith and controlling a load control system using messaging basedinterfaces.

FIG. 3 is a system diagram that illustrates a system for communicatingwith and controlling a load control system using messaging basedinterfaces and/or HTTP based interfaces.

FIG. 4 is a system diagram that illustrates another system forcommunicating with and controlling a load control system using messagingbased interfaces and/or HTTP based interfaces.

FIG. 5 is a system diagram that illustrates a further system forcommunicating with and controlling a load control system using messagingbased interfaces and/or HTTP based interfaces.

FIGS. 6A-6Z and 6AA show example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIGS. 7A-7B show further example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIGS. 8A-8D show still further example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIGS. 9A-9G show still further example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIGS. 10A-10C show further example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIGS. 11A-11Q show further example graphical user interfaces of anapplication that may allow a user to determine information on and tocontrol a load control system and/or control devices.

FIG. 12 is a block diagram of an example network device.

FIG. 13 is a block diagram of an example system controller.

FIG. 14 is a block diagram of an example control-target device.

FIG. 15 is a block diagram of an example control-source device.

DETAILED DESCRIPTION

FIG. 1 shows a high-level diagram of an example load control system 100.Load control system 100 may include a system controller 150 and loadcontrol devices for controlling (e.g., directly and/or indirectly) oneor more electrical loads in a user environment 102 (also referred toherein as a load control environment). Example user environments/loadcontrol environments 102 may include one or more rooms of a home, one ormore floors of a building, one or rooms of a hotel, etc. As one example,load control system 100 may enable the automated control of lightingsystems, shades, and heating, ventilating, and air conditioning (HVAC)systems in the user environment, among other electrical loads.

The load control devices of load control system 100 may include a systemcontroller 150, control-source devices (e.g., elements 108, 110, 120,and 122 discussed below), and control-target devices (e.g., elements112, 113, 116, 124, and 126 discussed below) (control-source devices andcontrol-target devices may be individually and/or collectively referredto herein as load control devices and/or control devices). The systemcontroller 150, the control-source devices, and the control-targetdevices may be configured to communicate (transmit and/or receive)messages, such as digital messages (although other types of messages maybe communicated), between one another using wireless signals 154 (e.g.,radio-frequency (RF) signals), although wired communications may also beused. “Digital” messages will be used herein for discussion purposesonly.

The control-source devices may include, for example, input devices thatare configured to detect conditions within the user environment 102(e.g., user inputs via switches, occupancy/vacancy conditions, changesin measured light intensities, and/or other input information) and inresponse to the detected conditions, transmit digital messages tocontrol-target devices that are configured to control electrical loadsin response to instructions or commands received in the digitalmessages. The control-target devices may include, for example, loadcontrol devices that are configured to receive digital messages from thecontrol-source devices and/or the system controller 150 and to controlrespective electrical loads in response to the received digitalmessages. A single control device of the load control system 100 mayoperate as both a control-source device and a control-target device.

According to one example, the system controller 150 may be configured toreceive the digital messages transmitted by the control-source devices,to interpret these messages based on a configuration of the load controlsystem, and to then transmit digital messages to the control-targetdevices for the control-target devices to then control respectiveelectrical loads. In other words, the control-source devices and thecontrol-target device may communicate via the system controller 150.According to another and/or additional example, the control-sourcedevices may directly communicate with the control-target devices withoutthe assistance of the system controller 150. The system controller maystill monitor such communications. According to a further and/oradditional example, the system controller 150 may originate and thencommunicate digital messages with control-source devices and/orcontrol-target devices. Such communications by the system controller 150may include programming/configuration data (e.g., settings) for thecontrol devices, such as configuring scene buttons on light switches.Communications from the system controller 150 may also include, forexample, messages directed to control-target devices and that containinstructions or commands for the control-target devices to controlrespective electrical loads in response to the received messages. Forexample, the system controller 150 may communicate messages to changelight levels, to change shade levels, to change HVAC settings, etc.These are examples and other examples are possible.

Communications between the system controller 150, the control-sourcedevices, and the control-target devices may be via a wired and/orwireless communications network as indicated above. One example of awireless communications network may be a wireless LAN where the systemcontroller, control-source devices, and the control-target devices maycommunicate via a router, for example, that is local to the userenvironment 102. For example, such a network may be a standard Wi-Finetwork. Another example of a wireless communications network may be apoint-to-point communications network where the system controller,control-source devices, and the control-target devices communicatedirectly with one another using, for example, Bluetooth, Wi-Fi Direct, aproprietary communication channel, such as CLEAR CONNECT™, etc. todirectly communicate. Other network configurations may be used such asthe system controller acting as an access point and providing one ormore wireless/wired based networks through which the system controller,the control-source devices, and the control-target devices maycommunicate.

For a control-target device to be responsive to messages from acontrol-source device, the control-source device may first need to beassociated with the control-target device. As one example of anassociation procedure, a control-source device may be associated with acontrol-target device by a user 142 actuating a button on thecontrol-source device and/or the control-target device. The actuation ofthe button on the control-source device and/or the control-target devicemay place the control-source device and/or the control-target device inan association mode for being associated with one another. In theassociation mode, the control-source device may transmit an associationmessage(s) to the control-target device (directly or through the systemcontroller). The association message from the control-source device mayinclude a unique identifier of the control-source device. Thecontrol-target device may locally store the unique identifier of thecontrol-source, such that the control-target device may be capable ofrecognizing digital messages (e.g., subsequent digital messages) fromthe control-source device that may include load control instructions orcommands. The control-target device may be configured to respond to thedigital messages from the associated control-source device bycontrolling a corresponding electrical load according to the loadcontrol instructions received in the digital messages. This is merelyone example of how control devices may communicate and be associatedwith one another and other examples are possible. According to anotherexample, the system controller 150 may receive configurationinstructions from a user that specify which control-source devicesshould control which control-target devices. Thereafter, the systemcontroller may communicate this configuration information to thecontrol-source devices and/or control-target devices.

As one example of a control-target device, load control system 100 mayinclude one or more lighting control devices, such as the lightingcontrol devices 112 and 113. The lighting control device 112 may be adimmer, an electronic switch, a ballast, a light emitting diode (LED)driver, and/or the like. The lighting control device 112 may beconfigured to directly control an amount of power provided to a lightingload(s), such as lighting load 114. The lighting control device 112 maybe configured to wirelessly receive digital messages via signals 154(e.g., messages originating from a control-source device and/or thesystem controller 150), and to control the lighting load 114 in responseto the received digital messages. One will recognize that lightingcontrol device 112 and lighting load 114 may be integral and thus partof the same fixture or may be separate.

The lighting control device 113 may be a wall-mounted dimmer, awall-mounted switch, or other keypad device for controlling a lightingload(s), such as lighting load 115. The lighting control device 113 maybe adapted to be mounted in a standard electrical wall box. The lightingcontrol device 113 may include one or more buttons for controlling thelighting load 115. The lighting control device 113 may include a toggleactuator. Actuations (e.g., successive actuations) of the toggleactuator may toggle (e.g., turn off and on) the lighting load 115. Thelighting control device 113 may include an intensity adjustment actuator(e.g., a rocker switch or intensity adjustment buttons). Actuations ofan upper portion or a lower portion of the intensity adjustment actuatormay respectively increase or decrease the amount of power delivered tothe lighting load 115 and thus increase or decrease the intensity of thereceptive lighting load from a minimum intensity (e.g., approximately1%) to a maximum intensity (e.g., approximately 100%). The lightingcontrol device 113 may include a plurality (two or more) of visualindicators, e.g., light-emitting diodes (LEDs), which may be arranged ina linear array and that may illuminate to provide feedback of theintensity of the lighting load 115.

The lighting control device 113 may be configured to wirelessly receivedigital messages via wireless signals 154 (e.g., messages originatingfrom a control-source device and/or the system controller 150). Thelighting control device 113 may be configured to control the lightingload 115 in response to the received digital messages.

The load control system 100 may include one or more other control-targetdevices, such as a motorized window treatment 116 for directlycontrolling the covering material 118 (e.g., via an electrical motor);ceiling fans; a table top or plug-in load control device 126 fordirectly controlling a floor lamp 128, a desk lamp, and/or otherelectrical loads that may be plugged into the plug-in load controldevice 126; and/or a temperature control device 124 (e.g., thermostat)for directly controlling an HVAC system (not shown). The load controlsystem 100 may also, or alternatively, include an audio control device(e.g., a speaker system) and/or a video control device (e.g., a devicecapable of streaming video content). Again, these devices may beconfigured to wirelessly receive digital messages via wireless signals154 (e.g., messages originating from a control-source device and/or thesystem controller 150). These devices may be configured to controlrespective electrical loads in response to the received digitalmessages.

Control-target devices, in addition to being configured to wirelesslyreceive digital messages via wireless signals and to control respectiveelectrical loads in response to the received digital messages, may alsobe configured to wirelessly transmit digital messages via wirelesssignals (e.g., to the system controller 150 and/or an associated controldevice(s)). A control-target device may communicate such messages toconfirm receipt of messages and actions taken, to report status (e.g.,light levels), etc. Again, control-target devices may also oralternatively communicate via wired communications.

With respect to control-source devices, the load control system 100 mayinclude one or more remote-control devices 122, one or more occupancysensors 110, one or more daylight sensors 108, and/or one or more windowsensors 120. The control-source devices may wirelessly send orcommunicate digital messages via wireless signals, such as signals 154,to associated control-target devices for controlling an electrical load.The remote-control device 122 may send digital messages for controllingone or more control-target devices after actuation of one or morebuttons on the remote-control device 122. One or more buttons maycorrespond to a preset scene for controlling the lighting load 115, forexample. The occupancy sensor 110 may send digital messages tocontrol-target devices in response to an occupancy and/or vacancycondition (e.g., movement or lack of movement) that is sensed within itsobservable area. The daylight sensor 108 may send digital messages tocontrol-target devices in response to the detection of an amount oflight within its observable area. The window sensor 120 may send digitalmessages to control-target devices in response to a measured level oflight received from outside of the user environment 102. For example,the window sensor 120 may detect when sunlight is directly shining intothe window sensor 120, is reflected onto the window sensor 120, and/oris blocked by external means, such as clouds or a building. The windowsensor 120 may send digital messages indicating the measured lightlevel. The load control system 100 may include one or more othercontrol-source devices. Again, one will recognize that control-sourcedevices may also or alternatively communicate via wired communications.

Turning again to the system controller 150, it may facilitate thecommunication of messages from control-source devices to associatedcontrol-target devices and/or monitor such messages as indicated above,thereby knowing when a control-source device detects an event and when acontrol-target device is changing the status/state of an electricalload. It may communicate programming/configuration information to thecontrol devices. It may also be the source of control messages tocontrol-target devices, for example, instructing the devices to controlcorresponding electrical loads. As one example of the later, the systemcontroller may run one or more time-clock operations that automaticallycommunicates messages to control-target devices based on configuredschedules (e.g., commands to lighting control device 113 to adjust light115, commands to motorized window treatment 116 for directly controllingthe covering material 118, etc.) For description purposes only, shadeswill be used herein to describe functions and features related tomotorized window treatments. Nonetheless, one will recognize thatfeatures and functions described herein are applicable to other types ofwindow coverings such as drapes, curtains, blinds, etc. Other examplesare possible.

According to a further aspect of load control system 100, the systemcontroller 150 may be configured to communicate with one or more networkdevices 144 in use by a user(s) 142, for example. The network device 144may include a personal computer (PC), a laptop, a tablet, a smart phone,or equivalent device. The system controller 150 and the network device144 may communicate via a wired and/or wireless communications network.The communications network may be the same network used by the systemcontroller and the control devices, or may be a different network (e.g.,a wireless communications network using wireless signals 152). As oneexample, the system controller 150 and the network device 144 maycommunicate over a wireless LAN (e.g., that is local to the userenvironment 102). For example, such a network may be a standard Wi-Finetwork provided by a router local to the user environment 102. Asanother example, the system controller 150 and the network device 144may communicate directly with one-another using, for example, Bluetooth,Wi-Fi Direct, etc. Other examples are possible such as the systemcontroller acting as an access point and providing one or morewireless/wired based networks through which the system controller andnetwork device may communicate.

In general, the system controller 150 may be configured to allow a user142 of the network device 144 to determine, for example, theconfiguration of the user environment 102 and load control system 100,such as rooms in the environment, which control devices are in whichrooms (e.g., the location of the control devices within the userenvironment, such as which rooms), to determine the status and/orconfiguration of control devices (e.g., light levels, HVAC levels, shadelevels), to configure the system controller (e.g., to change time clockschedules), to issue commands to the system controller in order tocontrol and/or configure the control devices (e.g., change light levels,change HVAC levels, change shade levels, change presets, etc.), etc.Other examples are possible.

The load control system 100 of FIG. 1 may be configured such that thesystem controller 150 is only capable of communicating with a networkdevice 144 when that device is local to the system controller, in otherwords, for the two to directly communicate in a point-to-point fashionor through a local network specific to the user environment 102 (such asa network provided by a router that is local to the user environment).It may be advantageous to allow a user of network device 144 tocommunicate with the system controller 150 and to control the loadcontrol system 100 from remote locations, such as via the Internet orother public or private network. Similarly, it may be advantageous toallow third-party integrators to communicate with the system controller150 in order to provide enhanced services to users of user environment102. For example, a third-party integrator may provide other systemswithin user environment 102. It may be beneficial to integrate suchsystems with load control system 100.

Referring now to FIG. 2 there is shown an example system 200. System 200may include one or more user environments as represented by userenvironments 202 a and 202 b. More specifically, system 200 may beconfigured to support numerous user environments, with only two userenvironments 202 a and 202 b shown to assist in describing system 200.Each user environment may be substantially the same, each including arespective load control system 210 a and 210 b that includes arespective system controller 250 a and 250 b and respective controldevices 220 a and 220 b (e.g., control-source devices and/orcontrol-target devices). In general, the system controller 250 a and 250b and control devices 202 a and 202 b of load control systems 210 a and210 b may functionally operate similar to system controller 150 and thecontrol devices as discussed with respect to FIG. 1. Each userenvironment 202 a and 202 b of system 200 may differ in that the userenvironments may be owned by different entities. For example, each userenvironment may be a residential home owned by respectively differentusers/homeowners, may be a business, etc. or come combination thereof.For description purposes only, user environments 202 a and 202 b may bereferred to herein as residential homes that are owned/rented byhome-owners. Hence, each user environment may include different controldevices and different configurations of these control devices and systemcontrollers. In this fashion, system 200 may include numerous differenthomes, for example. As compared to load control system 100, system 200may include systems for a user and/or third party to interface with aload control system 210 a/210 b from a location remote from therespective user environments 202 a/202 b, such as over the Internet orother private or public network.

As indicated, each user environment 202 a and 202 b of system 200 mayinclude a respective system controller 250 a and 250 b (although a userenvironment may include more than one system controller) and controldevices, collectively represented as elements 220 a and 220 b (again,system controller 250 a and control devices 220 a may make up loadcontrol system 210 a, and system controller 250 b and control devices220 b may make up load control system 210 b). System 200 may alsoinclude one or more message brokers 270 and one or more network devices280 a and 280 b. Network devices 280 a and 280 b may represent computingdevices in use by respective users of respective user environments 202 aand 202 b. For example, network device 280 a may be a device (e.g., aphone, PC, a laptop, a tablet, a smart phone, or equivalent device) inuse by a home-owner of user environment 202 a, and network device 280 bmay be a device (e.g., a phone, etc.) in use by a home-owner of userenvironment 202 b. As another and/or additional example, network devices280 a and 280 b may be third-party integrators that provide services torespective users/home-owners of user environments 202 a and 202 b. Here,network devices 280 a and 280 b may each be one or more computingservers for example. Again, system 200 may include numerous networkdevices 280 a and 280 b, with only two being shown for descriptionpurposes. According to system 200, network devices 280 a and 280 b maybe remote from the user environments (e.g., not located within the userenvironments). Nonetheless, network devices 280 a and 280 b may also belocal to the user environments (e.g., located within the userenvironments) and communicate with system controllers 250 a and/or 250 busing the message broker 270 as described below.

System 200 may also include networks 282 and 283, which may includeprivate and/or public networks, such as the Internet. Networks 282 and283 may at least in part be the same network. In general, systemcontrollers 250 a and 250 b may be configured to communicate via network282 with message broker 270, and each network device 280 a and 280 b maybe configured to communicate via network 283 with the message broker270. Through the use of the message broker 270 and other mechanismsdescribed herein, a network device 280 a, for example, may communicatewith a system controller 250 a of user environment 202 a, for example,and interact with the control devices 220 a of that environment. As oneexample of system 200, a user may use network device 280 a tocommunicate with system controller 250 a and through thesecommunications, may determine, for example, the configuration of theload control system 210 a/user environment 202 a (e.g., such as rooms inthe environment and the location of the control devices within the userenvironment, such as which rooms), to determine the status and/orconfiguration of control devices 220 a (e.g. light levels, HVAC levels,shade levels), to configure the system controller 250 a (e.g., to changetime clock schedules), to issue commands to the system controller 250 ato control and/or configure the control devices 220 a (e.g., changelight levels, change HVAC levels, change shade levels, change presets,etc.). These are merely examples. As another example, a network device280 a that is operated by a third-party integrator may communicate withsystem controller 250 a to determine the status of and to control theload control system 210 a (as described herein), and to also use thisfunctionality to integrate the features of load control system 210 awith features of another system in the user environment 202 a that thethird-party integrator may have control over. As one example, athird-party integrator may be a home security provider and in responseto detecting an issue in the user environment 202 a through a systemprovided by the third-party integrator (e.g., an alarm system), instructthe system controller 250 a to actuate lights in the user environment.Other examples are possible. For example, a third-party integrator mayprovide one or more voice/speaker-based devices that are located in theuser environment 202 a. A user may audibly interface with such a device(e.g., through voice commands) which in turn may communicate with anetwork device 280 a (e.g., a computing server of the third-partyintegrator). Network device 280 a may in turn communicate with systemcontroller 250 a to control the load control system 210 a based on howthe user interfaced with the voice/speaker-based device. Alternatively,network device 280 a may communicate with system controller 250 a todetermine the status of the load control system 210 a and in turn maycommunicate with the voice/speaker-based device to audibly report thestatus to the user. Again, this is one example. In similar fashions,users and third-party integrators may communicate with any userenvironment of system 200.

Referring more specifically now to system controller 250 a (systemcontroller 250 b may be similarly configured), it may include one ormore general purpose processors, special purpose processors,conventional processors, digital signal processors (DSPs),microprocessors, microcontrollers, integrated circuits, programmablelogic devices (PLD), field programmable gate arrays (FPGA), applicationspecific integrated circuits (ASICs), or any suitable controller orprocessing device or the like (not shown) (hereinafter collectivelyreferred to as processor(s)), for example. The processor(s) of systemcontroller 250 a may be configured to execute one or more software-basedapplications and/or firmware based modules that include instructionsthat when executed by the processor(s), may configure the processor(s)to perform signal coding, data processing, input/output processing, orany other functions and/or features of the system controller asdescribed herein. These features and functions are represented in partby modules 252 and 260 in FIG. 2, which are further described below.Modules 252 and 260 may execute as one or more software-based processes,for example. One will also recognize that features, functions, andprocesses described herein may also and/or alternatively be provided byhardware in addition to and/or as an alternative to software-basedinstructions and processes. System controller 250 a may also include oneor more memory modules/devices (including volatile and non-volatilememory modules/devices) that may be communicatively coupled to theprocessor(s). The memory modules/devices may be implemented as one ormore external integrated circuits (IC) and/or as one or more internalcircuits of the processor(s). The one or more memory modules/devices maystore the software-based applications and may also provide an executionspace as the processors execute the applications. System controller 250a may also include one or more communicationinterfaces/transceivers/network interface devices (not shown)communicatively coupled to the processors and/or memory devices/modules.The communication interfaces may allow system controller 250 a tocommunicate over one or more wired and/or wireless communicationnetworks. As one example, the communication interfaces may allow systemcontroller 250 a to communicate wirelessly with control devices 220 a assimilarly described for load control system 100. The communicationinterfaces may also allow the system controller 250 a to communicatewirelessly and/or via a wired connection(s) with a router (not shown),for example, that is local to user environment 202 a and that providesthe user environment with a local network. Through this local network,the system controller 250 a may communicate with a network device 144that is local to the user environment 202 a, and may also communicateand with network 282 (such as through an Internet service provider, notshown). System controller 250 a may also include one or more databases254 as further described herein. These databases may be flat databases,relational/SQL databases, NoSQL/non SQL databases, and/or a time seriesdatabases, etc., although any form of database(s) may be used. Systemcontroller 250 a may also include one or more user interfaces such adisplay monitor, keyboard, mouse, speakers, audio receivers, etc. Whilesystem controller 250 a is shown as having example modules 252 and 260and example database 254, the system controller may include fewer,other, and/or additional modules and databases.

Referring more specifically to modules 252 and 260 and to database 254,database 254 may maintain configuration information of the load controlsystem 250 a. This information may include, for example, the controldevices 220 a of the load control system, the configuration of the userenvironment 202 a such as rooms in the environment, which controldevices 220 a are in which rooms, communication addresses of the controldevices needed to communicate with the devices, which control-sourcedevices may be controlled by/associated with which control-targetdevices, configuration information of the control devices (e.g., buttonscene configurations, occupancy/vacancy sensor configurations, etc.),system configurations such as time clock schedules, etc. The databasemay also maintain status information of the control devices (e.g., errorconditions, light levels, shade levels, HVAC levels, power consumptionlevels, etc.). The database may also maintain event-based information,as referred to below, which may include a record of events as they occurwithin the system. These are merely examples, and other and/oradditional or less information may be possible.

Module 252 may be referred to herein as the core module or core 252 fordescription purposes and may be configured to execute as one or moresoftware based processes. Core 252 may be configured to act as acommunications module between the control devices 220 a and the systemcontroller, assisting in and/or monitoring communications betweencontrol-source devices and control-target devices and storing relatedinformation in database 254. This information may include, for example,changes to which control-source devices are associated with whichcontrol-target devices. The information may also include event-basedinformation, such as (i) events detected by control-source devices(e.g., occupancy/vacancy as detected by sensor 110, light levels asdetected by sensors 108 and 120, detection of buttons actuated on remotecontrol devices 113 or wall panels/switches 113, etc.), (ii) commandscommunicated by control-source devices to control-target devices toalter settings based on detected events (e.g., changes to light levels,shade levels, HVAC levels, etc.), and (iii) commands from control-targetdevices indicting/confirming altered settings. Core 252 may receivestatus messages directly from control devices, such as error conditions,light levels, shade levels, HVAC levels, power consumption levels,occupancy/vacancy conditions, etc. and store such information indatabase 254. Core 252 may also run time clock schedules, andcommunicate messages to the control devices in accordance with thoseschedules. Again, core 252 may store such changes to the control devicesand/or acknowledgements from the control devices in database 254. Core252 may also communicate information/messages to module 260 (which maybe referred to as the gateway module or gateway 260 for descriptionpurposes) as described below. Core 252 may receive messages from thegateway 260 that may result in the core changing configurationparameters of the system controller (e.g., time clock settings), orcommunicating messages to the control devices (such as changes to lightlevels), or adjusting configuration/operating parameters of the controldevices (e.g., change scene buttons on switch buttons, occupancy/vacancysensor configurations), etc. Core 252 may respond back to the gateway260 after it performs such operations. Core 252 may also receive fromthe gateway 260 requests for any of the information stored in thedatabase 254 as discussed above, and report that information back to thegateway. These are examples and core 252 may perform other and/oradditional functions and operations.

Turning to gateway 260, it may be configured to act as an interfacebetween the system controller 250 a and external devices, such as localnetwork device 144 situated in the user environment 202 a and remotenetwork devices 280 a and 280 b. For example, gateway 260 may receivemessages from network device 144 and/or network devices 280 a and/or 280b and route those messages within the system controller 250 a, such asto core 252 for execution. Gateway 260 may also receive responses tosuch messages, such as from core 252, and route them back to the networkdevices 144, 280 a and/or 280 b. Gateway 260 may also receive, forexample, status and event based information, such as from core 252, androute that information to network devices 144, 280 a and/or 280 b. Theseare examples and other examples are possible. To perform such functionsand operations, gateway 260 may include an API (application programminginterface) server 264, a local shell client (also referred to herein asshell client) 262, and an MQTT (message queue telemetry transport)client 266. Each of the API server 264, the local shell client 262, andthe MQTT client 266 may operate as one or more software based processeswithin the system controller 250 a, although other configurations arepossible. One will recognize that the names API server, local shellclient, and MQTT client as used herein are for description purposesonly.

Local shell client 262 may be configured to function or operate as aninterface point to network devices 144 that are local to the systemcontroller 250 a (e.g., that are on the same local network as the systemcontroller and/or are located in within user environment 202 a). Localshell client 262 may be configured to support a communicationsconnection 234 with network device 144. This connection may be, forexample, a TCP/IP (transmission control protocol/internet protocol) orUDP/IP (user datagram protocol) based connection, although otherconnections may be used. Local shell client 262 may provide a shell typeinterface (e.g., a command-line type interface) to network device 144over the connection. The interface may be a secure shell interface(e.g., use the secure shell (SSH) protocol). One will recognize thatwhile local shell client 262 is described herein as an interface pointto network devices 144 that are local to the system controller 250 a, anetwork device that is on a different network as the system controller(i.e., not on the same local network as the system controller) and/ornot located in within user environment 202 a may also use local shellclient 262 to communicate with the system controller.

MQTT client 266 may be configured to function or operate as an interfacepoint to the message broker 270 and therefore as an interface point tonetwork devices 280 a and 280 b that are remote to the system controller250 a. MQTT client 266 may support a communications connection 230 awith the message broker 270. This connection may be, for example, aTCP/IP based connection although other connections may be used. On topof this connection the MQTT client 266 may support the MQTTpublish-subscribe-based messaging protocol, for example, with themessage broker 270, with the MQTT client 266 acting as a client to thebroker. As further described below, MQTT client 266 may send messagesout of the system controller to the message broker and thus to networkdevices 280 a and/or 280 b by publishing messages to one or more definedtopics, as that term is used in messaging based protocols. Similarly,MQTT client 266 may receive messages from the message broker thatoriginate from network devices 280 a and/or 280 b, for example, bysubscribing to one or more defined topics.

The system controller 250 a may support an application programminginterface (API) that may include set of well-defined commands andresponses (generically referred to herein as and API or as “APImessages”) to interact with network devices 144, 280 a and/or 280 b.Service-based applications (e.g., software-based applications) providedby or that execute on the network devices 144, 280 a, and/or 280 b mayuse the API to interact with the system controller. API server 264 mayoperate as a point of origination and termination within the systemcontroller 250 a for these communications. For example, a network device144, 280 a, and/or 280 b may execute one or more software-basedapplications that provide a defined set of services to a user. Theseservices may be based at least in part on interactions with systemcontroller 250 a. For example, network device 144 may provide asoftware-based application to a user that allows a user to controllights or shades within the user environment 202 a. Similarly, networkdevice 280 a may provide a software-based application to a user thatallows a user to control lights or shades from a location external tothe user environment. As another example, network device 280 a mayprovide an alarm based service as described above.

To provide such services, the network devices may use the API of thesystem controller 250 a to communicate API messages to the systemcontroller 250 a. For example, network device 144 may communicate an APImessage to local shell client 262, which may then forward that messageto the API server 264 which may then interpret and execute the message.Similarly, network device 280 a may communicate an API message throughthe message broker 270 to the MQTT client 266, which may then forwardthat message to the API server 264 which may then interpret and executethe message. To execute/interpret an API message, the API server 264 maycommunicate the message (or a translated form of the message) to core252 to provide/execute the message, the API server may communicate withdatabase 254 to retrieve and/or store information, and/or the API servermay handle the message itself. Other examples are possible.

Similarly, to provide such services, the system controller 250 a maycommunicate API messages to the network devices 144, 280 a, and/or 280b. For example, core 252 may communicate information that is intendedfor the network devices by sending that information to the API server264. This information may include responses to or results from messagesreceived from the network devices and executed by core 252 (e.g.,messages to control the control devices 220 a). This information mayinclude information core 252 retrieves from database 254 in response tomessages received from the network devices. Similarly, API server 264may retrieve information directly from database 254 in response tomessages received from the network devices. As API server 264 receivesinformation from core 252 and/or database 254, for example, it mayformat that information according to an appropriate API message(s) andthen forward the messages to local shell client 262 for forwarding tonetwork device 144, and/or forward the messages to MQTT client 266 forforwarding to the message broker 270 and to network devices 280 a and/or280 b. Other examples are possible.

With respect to information flowing out of the system controller 250 ato the network devices 144, 280 a, and/or 280 b, in some instances, theinformation may be responsive to messages received from the networkdevices, as indicated above. In some cases, API server 264 maycommunicate such responsive messages to both local shell client 262 andMQTT client 266, regardless of where the original message originated(i.e., from a network device via local shell client 262 or a networkdevice via MQTT client 266). In other cases, the API server may forwardthe response messages to only one or the other of the local shell client262 and MQTT client 266, depending on which interface the originalmessage originated.

According to a further aspect of system controller 250 a, core 252 mayconstantly report to API server 264 status and/or event basedinformation that originates from within the load control system 210 a.For example, the core 252 (i) may report to API server 264 eventsdetected by control-source devices from within the user environment 202a (e.g., occupancy/vacancy as detected by sensor 110, light levels asdetected by sensors 108 and 120, detection of buttons actuated on remotecontrol devices 113 or wall panels/switches 113, etc.), (ii) may reportto API server 264 changes in the states of the electrical loads (e.g.,changes to light levels, shade levels, HVAC/thermostat levels/readings,etc.) that may result from messages from control-source devices, and(iii) may report to API server 264 changes in the states of theelectrical loads due to time clock events, for example. The core 252 mayalso report to API server 264 changes to the configuration of the loadcontrol system, such as the addition of new control devices, thechanging of or creation of associations between control-source andcontrol-target devices, etc. In general, any such information the APIserver 264 receives from core 252, API server 264 may forward as an APImessage to local shell client 262 and/or MQTT client 266 for forwardingto network device 144 and the message broker 270 and thus networkdevices 280 a and/or 280 b. In this fashion, network devices may be keptapprised of the state of the load control system 210 a in a “real-time”fashion without having to query the load control system for its state.

Referring now more specifically to MQTT client 266, the message broker270 (note that one message broker 270 is shown in FIG. 2; nonetheless,one will recognize that system 200 may include multiple messagebrokers), and the network devices 280 a and 280 b, each network device280 a and 280 b may include a client process that supports a respectiveconnection 232 a and 232 b (e.g., a TCP/IP connection, although otherconnections may be used) with the message broker 270, and that maysupport over this connection the MQTT publish-subscribe-based messagingprotocol with the message broker, for example. The message broker 270may be one or more computing devices (e.g., one or more computingservers) that function as an MQTT message broker, supporting the MQTTpublish-subscribe messaging protocol, for example. The computing devicesof message broker 270 may include one or more general purposeprocessors, special purpose processors, conventional processors, digitalsignal processors (DSPs), microprocessors, microcontrollers, integratedcircuits, programmable logic devices (PLD), field programmable gatearrays (FPGA), application specific integrated circuits (ASICs), or anysuitable controller or processing device or the like (hereinaftercollectively referred to as processor(s)) (not shown), for example. Theprocessor(s) of message broker 270 may be configured to execute one ormore software-based applications and/or firmware based modules thatinclude instructions that when executed by the processor(s) mayconfigure the processor(s) to perform signal coding, data processing,input/output processing, or any other function or operation thatconfigures the message broker 270 to provide MQTT message brokerfunctionality and operations as described herein. One will alsorecognize that features, functions, and processes described herein ofthe message broker 270 may also and/or alternatively be provided byhardware in addition to and/or as an alternative to software-basedinstructions and processes. The message broker 270 may also include oneor more memory modules/devices (including volatile and non-volatilememory modules/devices) that may be communicatively coupled to theprocessor(s). The memory modules/devices may be implemented as one ormore external integrated circuits (IC) and/or as one or more internalcircuits of the processor(s). The one or more memory modules/devices maystore the software-based applications and may also provide an executionspace as the processors execute applications. The message broker 270 mayalso include one or more communication interfaces/transceivers/networkinterface devices (not shown) communicatively coupled to the processorsand/or memory devices/modules. The communication interfaces may allowthe message broker 270 to communicate over one or more wired and/orwireless communication networks, such as network 282 and 283.

As the MQTT clients 266 of the respective system controllers 250 a and250 b establish respective connections 230 a and 230 b with the messagebroker 270 and form respective MQTT connections over connections 230 aand 230 b with the message broker, for example, the message broker maystart a respective process (such as a software-based process) 272 a and272 b, for example, with each MQTT client 266. Similarly, as eachnetwork device 280 a and 280 b establishes a respective connection 232 aand 232 b with the message broker 270, for example, the message brokermay start a respective process (such as a software-based process) 274 aand 274 b with each network device. In accordance with one example ofthe MQTT protocol, the message broker 270 may receive respective APImessages from the MQTT clients 266 via connections 230 a and 230 b atprocesses 272 a and 272 b respectively, and forward those messages toprocesses 274 a and/or 274 b. Processes 274 a and 274 b may subsequentlyforward the API messages over connections 232 a and 232 b respectivelyto network devices 280 a and 280 b. Similarly, the message broker 270may receive respective API messages from the network devices 280 a and280 b via connections 232 a and 232 b at processes 274 a and 274 brespectively, and forward those API messages to processes 272 a and/or272 b. Processes 272 a and 272 b may subsequently forward the APImessages over connections 230 a and 230 b to MQTT clients 266respectively of the system controllers 250 a and 250 b. In general,network devices 280 a and 280 b may proceed through an authenticationprocess with the message broker 270 before the message broker mayforward messages between the network devices and system controllers.

In accordance with an example of the MQTT protocol, as the MQTT client266 of system controller 250 a, for example, receives API messages fromthe API server 264, it may communicate those messages over connection230 a to the message broker 270 by publishing the API messages to adefined topic “A”. Assuming network device 280 a, for example, desiresto receive information from the system controller 250 a, it maysubscribe with the message broker 270 to that same topic “A”. Havingsubscribed to topic “A”, message broker 270 may forward the API messagesit receives from system controller 250 a over connection 232 a atprocess 272 a to network device 280 a via process 274 a. Similarly, fornetwork device 280 a to communicate an API message to the systemcontroller 250 a, it may communicate those messages over connection 232a to process 274 a at the message broker 270 by publishing the APImessages to a defined topic “B” (one will recognize topics A and B maythe same or different). To receive API messages from network device 280a, MQTT client 266 of system controller 250 a may subscribe with themessage broker to topic “B”. Having subscribed to topic “B”, messagebroker 270 may forward the API messages it receives from network device280 a at process 274 a to the MQTT client 266 of system controller 250 aover connection 230 a via process 272 a. Other examples are possible.

With specific reference now to topics as described above, according toone example, each system controller 250 a and 250 b of system 200 mayhave an assigned communications address, such as a MAC address (mediaaccess control address) (or possibly more than one address). This may bethe address assigned to the communication interface or transceiver ornetwork interface device of the system controller 250 a and 250 b thatsupports connection 230 a and 230 b respectively with the messagebroker, for example (A MAC address will be used herein for descriptionpurposes. Nonetheless, a different address assigned to each systemcontroller may alternatively be used in place of a MAC address asdiscussed herein (such as with topics)). The MAC address of each systemcontroller 250 a and 250 b of system 200 may be different/unique. Inthis example, system controller 250 a may have the MAC address“A1:B1:C1:D1:E1:F1” and system controller 250 b may have the MAC address“A2:B2:C2:D2:E2:F2” (as shown by callouts 222 a and 222 b). MACaddresses are further discussed below. According to a further aspect ofsystem 200, each system controller 250 a and 250 b may be assigned aUnique Identifier (ID) Value (Unique ID Value), which may be a randomvalue. In this example, system controller 250 a may have the Unique IDValue of “ABC123” and system controller 250 b may have the Unique IDValue of “ABC789” (as shown by callouts 222 a and 222 b). These are onlyexamples. According to a still further aspect of system 200, all systemscontrollers 250 a and 250 b of system 200 may be assigned a commonuniversal identifier. In this example, each system controller 250 a and250 b has the common universal identifier of “1201” (as shown bycallouts 222 a and 222 b). Again, these are merely examples. (One willrecognize that while a system controller may be described herein ashaving associated with it a unique identifier, MAC address, anduniversal identifier, these values may also be viewed in general asbeing associated with a system controller's respective load controlsystem and/or respective user environment). Topics used by systemcontrollers 250 a and 250 b and network devices 280 a and 280 b ofsystem 200 may have a format that uses, for example, (i) the Unique IDValue assigned to a system controller 250 a/250 b, (ii) the universalidentifier assigned to all system controllers, and (iii) one of severaldifferent topic identifiers/values, such as “Request” and “Response”,although additional and/or other values may be used. As one example, theformat of the topics used by system 200 may be of the form:“/u/Universal-Identifier/d/System-Controller-ID/Topic-Identifier”, whereUniversal-Identifier may be “1201”, System-Controller-ID may be “ABC123”or “ABC789”, and Topic-Identifier may be “Request” or “Response” in thisexample. Again, this is merely an example and other variations arepossible. For example, topics used by system controllers 250 a and 250 band network devices 280 a and 280 b of system 200 may have a format thatuses, for example, (i) the MAC address assigned to a system controller250 a/250 b, (ii) the universal identifier assigned to all systemcontrollers, and (iii) one of several different topicidentifiers/values, such as “Request” and “Response”, althoughadditional and/or other values may be used. As one example, the formatof the topics used by system 200 may be of the form:“/u/Universal-Identifier/d/MAC-Address/Topic-Identifier”, whereUniversal-Identifier may be “1201”, MAC-Address may be“A1:B1:C1:D1:E1:F1” or “A2:B2:C2:D2:E2:F2”, and Topic-Identifier may be“Request” or “Response”. In one aspect, these two examples are similarin that each uses a universal identifier, a unique identifier (e.g., aMAC address of a system controller or the Unique ID Value assigned to asystem controller), and a topic identifier/value. For ease ofdescription, example systems will be described herein using topics ofthe form:“/u/Universal-Identifier/d/System-Controller-ID/Topic-Identifier”.Again, other variations are possible and may be used.

According to one example, each time the MQTT client 266 of systemcontroller 250 a sends an API message to the message broker 270, it maypublish the API message to the broker together with the topic“/u/1201/d/ABC123/Response”. Similarly, each time the MQTT client 266 ofsystem controller 250 b sends an API message to the message broker 270,it may publish the API message to the broker together with the topic“/u/1201/d/ABC789/Response”. If network device 280 a, for example,wishes to receive API messages from system controller 250 a, forexample, it may subscribe with the message broker to the topic“/u/1202/d/ABC123/Response” (one will recognize that network device 280a may only need to subscribe to a portion of this topic, such as“/u/#/d/ABC123/Response”, where “#” represents a wildcard value).Similarly, if network device 280 a, for example, wishes to receive APImessages from system controller 250 b, it may subscribe with the messagebroker to the topic “/u/1202/d/ABC789/Response” (or simply“/u/#/d/ABC789/Response”, e.g.). In this fashion, as the message brokerreceives API messages published by the system controllers 250 a and 250b, it may examine the associated topics, determine which network devices280 a and 280 b may have subscribed to the topics (at least in part),and forward the messages via processes 272 a/272 b and 274 a/274 b. Ascan be seen, through the use of the System-Controller-ID, a networkdevice 280 a and 280 b may receive API messages from a desired systemcontroller 250 a and 250 b.

According to a further example, each time network device 280 a, forexample, wishes to send an API message to system controller 250 a, itmay publish the message to the message broker 270 using the topic“/u/1202/d/ABC123/Request”. Similarly, each time network device 280 a,for example, wishes to send an API message to system controller 250 b,it may publish the message to the message broker 270 using the topic“/u/1202/d/ABC789/Request”. In other words, through the use of theSystem-Controller-ID, a network device 280 a and 280 b may communicatewith a desired system controller 250 a and 250 b. For system controller250 a to receive API messages from network device 280 a, MQTT client 266of system controller 250 a may subscribe to the topic“/u/1202/d/ABC123/Request” (or simply “/u/#/d/ABC123/Request”, e.g.).Similarly, for system controller 250 b to receive API messages fromnetwork device 280 a, MQTT client 266 of system controller 250 b maysubscribe to the topic “/u/1202/d/ABC789/Request” (or simply“/u/#/d/ABC123/Request”, e.g.). In this fashion, as the message broker270 receives API messages published by the network devices 280 a and 280b, it may examine the associated topics, determine which systemcontrollers may have subscribed to the topics (at least in part), andforward the messages via processes 274 a/74 b and 272 a/272 b. Hence,through the use of the System-Controller-ID, a network device 280 a and280 b may send API messages to a desired system controller 250 a and 250b.

As described above, the system controllers 250 a and 250 b maycontinuously publish API messages to the message broker 270 as eventsoccur within the respective load control systems, in addition topublishing API messages that are responsive to commands from networkdevices. Network devices 280 a and 280 b that are subscribed to receiveAPI messages from a respective system controller (e.g., that subscribeto the “Response” based topic and the System-Controller-ID of the systemcontroller) may in turn continuously receive the API messages. If nonetwork device 280 a and 280 b is subscribed to receive messagespublished by a respective system controller 250 a and 250 b, the messagebroker may simply discard the message. Multiple network devices 280 aand 280 b may also subscribe at the same time to receive API messagesfrom a given system controller. As can also be seen from the above, anetwork device 280 a and 280 b may communicate specific commands toand/or request information from a specific system controller 250 a and250 b by publishing an API message to the message broker using a“Request” based topic and the appropriate System-Controller-ID for thatsystem controller. Similarly, the network device may receive a responseto the API message from the respective system controller by subscribingwith the message broker 270 for messages having the “Response” basedtopic and the appropriate System-Controller-ID.

While system 200 is described herein as being based on the MQTTprotocol, other message based protocols may be used, such as theAdvanced Message Queuing Protocol (AMQP).

System 200 uses an MQTT message-based system for a network device 280 aand 280 b to communicate with a system controller 250 a and/or 250 b ofa respective user environment 202 a and 202 b. Turning now to FIG. 3there is shown an example system 300. While system 200 uses an MQTTmessage-based system for a network device 280 a and 280 b to communicatewith a system controller 250 a and/or 250 b, system 300 allows a networkdevice 380, for example, to communicate with a system controller 250 aand/or 250 b using an HTTP (Hypertext Transfer Protocol) basedinterface. Network device 380 may be similar to network devices 280 aand 280 b in that it may be a device in use by a user (e.g., ahome-owner of a user environment) and/or may be a third-party integratorconfigured to provide a service(s) based on interactions with respectivesystem controllers 250 a and/or 250 b through the API supported by thesecontrollers. In particular, system 300 may allow a network device 380 toreceive API messages published by respective system controllers 250 aand 250 b using an HTTP interface. The information of these API messagesmay include for example, event and status based information occurring ina respective load control system 210 a and 210 b and that iscontinuously published by the system controllers 250 a and 250 b to themessage broker 370 (it may also include API messages that are responsiveto messages from network devices). Example system 400 of FIG. 4, whichis discussed below, shows an example system that further allows networkdevice 380 to communicate API messages to (and receive responses from)respective system controllers 250 a and 250 b using an HTTP interface.While FIG. 3 shows only one network device 380, there may be numeroussuch devices in system 300.

System 300 may include one or more message brokers 370 (one shown here)that may operate similar to message broker 270 as described for system200. System 300 may also include one or more user environments 202 a and202 b and respective system controllers 250 a and 250 b (and associatedcontrol devices 220 a and 220 b) that may have MQTT interfaces withmessage broker 370, and may also include one or more network devices 280a and 280 b that may communicate through MQTT interfaces with messagebroker 370. System controllers 250 a and 250 b, message broker 370, andnetwork devices 280 a and 280 b may similarly operate as described forsystem 200. System 300 may now also include one or more data aggregators310 (one shown here), one or more web servers 340 (one shown here), andone or more network devices 380 that may communicate with web server 340(where the or more network devices are represented as network device 380in FIG. 3).

Again, while system 300 is described herein as being based on the MQTTprotocol, other message based protocols may be used, such as theAdvanced Message Queuing Protocol (AMQP).

The data aggregator 310 may be one or more computing devices (e.g., oneor more computing servers) that may include one or more general purposeprocessors, special purpose processors, conventional processors, digitalsignal processors (DSPs), microprocessors, microcontrollers, integratedcircuits, programmable logic devices (PLD), field programmable gatearrays (FPGA), application specific integrated circuits (ASICs), or anysuitable controller or processing device or the like (hereinaftercollectively referred to as processor(s)) (not shown), for example. Theprocessor(s) of data aggregator 310 may be configured to execute one ormore software-based applications and/or firmware based modules thatinclude instructions that when executed by the processor(s) mayconfigure the processor(s) to perform signal coding, data processing,input/output processing, or any other function that configures the dataaggregator to operate as described herein. One will also recognize thatfeatures, functions, and processes of data aggregator 310 describedherein may also and/or alternatively be provided by hardware in additionto and/or as an alternative to software-based instructions andprocesses. Data aggregator 310 may also include one or more memorymodules/devices (including volatile and non-volatile memorymodules/devices) that may be communicatively coupled to theprocessor(s). The memory modules/devices may be implemented as one ormore external integrated circuits (IC) and/or as one or more internalcircuits of the processor(s). The one or more memory modules/devices maystore the software-based applications and may also provide an executionspace as the processors execute applications. Data aggregator 310 mayalso include one or more communication interfaces/transceivers/networkinterface devices (not shown) communicatively coupled to the processorsand/or memory devices/modules. The communication interfaces may allowdata aggregator 310 to communicate over one or more wired and/orwireless communication networks (not shown) with the message broker 370and the web server 340. The data aggregator 310 may also include one ormore user interfaces such a display monitor, keyboard, mouse, speakers,audio receivers, etc.

The data aggregator 310 may include an MQTT client module 312 (alsoreferred to herein as MQTT client), a pipe module 314 (also referred toherein as pipe), and a filters module 316 (also referred to herein asfilters) (One will recognize that the names data aggregator, MQTTclient, and pipe as used herein are for description purposes only). Eachof these modules may be configured to operate as one or more softwarebased processes within the data aggregator, although otherconfigurations may be used. While data aggregator 310 is shown as havingexample modules 312, 314, and 316 the aggregator may include fewer,other, and/or additional modules. Starting with MQTT client 312, it maybe configured to support a communications connection 332 with themessage broker 370. This connection may be, for example, a TCP/IP basedconnection, although other connections may be used. On top of thisconnection the MQTT client 312 may support the MQTTpublish-subscribe-based messaging protocol with the message broker 370,with the MQTT client 312 acting as a client to the message broker. Asthe MQTT client 312 of the data aggregator 310 establishes connection332 with the message broker and forms an MQTT connection to the brokerfor example, the message broker may start a respective process 376 withthe MQTT client 312. According to one example, MQTT client 312 maysubscribe with the message broker 370 to the topic“/u/1202/d/#/Response” (where “#” represents a wildcard value). Bysubscribing to a topic that uses the Universal-Identifier (here “1201”)common to all system controllers 250 a and 250 b, the message broker 370may forward from respective processes 272 a/272 b to process 376 all APImessages published by the system controllers 250 a and 250 b to themessage broker 370 that use the “Response” based topic. In turn, process376 may forward the API messages to MQTT client 312 via connection 332.One will recognize that other topics may also be used. For example, MQTTclient 312 may also subscribe with the message broker 370 to the topic“/u/1202/d/#/Request” (or alternatively, to the topic “/u/1202/d/#/#”).Here, the message broker 370 may also forward from respective processes274 a/274 b to process 376 (and thus the MQTT client 312) all APImessages published by the network devices 280 a and 280 b to the messagebroker 370 that use the “Request” based topic. Again, these are merelyexamples and other mechanisms may be used for the message broker 370 toforward API messages to the data aggregator 310. For example, the dataaggregator may subscribe to receive API messages from a specific set ofsystem controllers, for example, by specifying the full topic used bythe respective controllers (e.g., “/u/1202/d/ABC123/Response” and“/u/1202/d/ABC789/Response”). Assuming the data aggregator onlysubscribes to “Response” based topics from all system controllers 250 aand 250 b, as the message broker passes API messages to process 376, theprocess may in turn communicate the API messages to the MQTT client 312via connection 332. Process 376 may also communicate, with the APImessages, the full topic to which an API message was published by therespective system controller 250 a and 250 b (i.e., the topic mayinclude the System-Controller-ID of the respective system controller,such as “/u/1202/d/ABC123/Request” or “/u/1202/d/ABC789/Request”). Asthe MQTT client 312 receives API messages (and the associated topics)from the message broker 370, it may forward the API messages/topics topipe module 314.

Pipe module 314 may be configured to function as a data cache/messagequeue, for example, that receives API messages and possibly topics fromMQTT client 312, that processes the API messages (e.g. aggregatesseveral API messages into larger blocks for data efficiency), thatplaces/writes the API messages in a message queue, and that controls thereading of the API messages from the message queue by filters 316 forfurther processing. According to another example, pipe module 314 may bemultiple message queue, with MQTT client 312 putting API messages intorespective ones of the queues. In this way, pipe module 314 may act astemporary storage until API messages are processed by filters 316, asdescribed below. According to another aspect, depending on the number ofuser environments 202 a and 202 b/load control systems 210 a and 210 bin system 300, there may be multiple message brokers 370, with differentmessage brokers servicing different system controllers 250 a and 250 b.Here, data aggregator 310 may have multiple MQTT clients 312, each to arespective message broker. According to this example, pipe module 314may receive API messages from each MQTT client 312 and aggregate thesemessages into one message queue or multiple message queues (e.g., onemessage queue for each MQTT client) for processing by the filters 316.

Filters 316 may represent one or more modules (which may operate as oneor more software-based processes for example) that read and/or receiveAPI messages (and associated topics) from pipe module 314, that filterthose API messages based on one or more criteria, and that then forwardsresulting information to one or more destinations. In one aspect, theremay be multiple filter modules executing at any given time, eachanalyzing the same API messages read/received from pipe module 314, andeach searching for and analyzing specific data and routing resultinginformation to a respective destination. According to another aspect,assuming pipe module 314 is multiple message queues, each queue may haverespective filter(s). The filters 316 may be dynamic in that anadministrator may change the filters depending on a desiredconfiguration of system 300. The filters 316 may filter based onspecific fields of the API messages themselves and/or on the topicsassociated with respective API messages. Different filters may beconfigured to have different functions. For example, one filter mayoperate to simply remove/discard certain types of API messages (e.g.,there may be certain status information produced by the systemcontrollers 250 a and 250 b that are not needed by network device 380)and route the remaining API messages (and associated topics) to acertain destination. Another filter may be configured to operate tosearch for and detect certain API messages and/or topics and route thoseAPI messages (and associated topics) to a certain destination. Anotherfilter 316 may be configured to perform operations on API messagesread/received from pipe module 314 (such as performing statisticalanalysis on the API messages) and forward the results to a specificdestination. One will recognize that other examples are possible.

According to example system 300, filters 316 may have a communicationsconnection 334 with web server 340. This connection may be, for example,a TCP/IP or UDP/IP based connection, although other types of connectionsmay be used. Web server 340 may support an HTTP/HTTPS (HypertextTransfer Protocol/secure Hypertext Transfer Protocol) interface on thisconnection with standard methods (such as GET, PUT, POST, DELETE, etc.),although one will recognize that other interfaces may be used. Asfilters 316 receives API messages from pipe module 314, it may discardcertain messages based on one or more fields of the messages andcommunicate the remaining API messages (together with their respectivetopics as published by the system controllers 250 a and 250 b, forexample) to the web server 340 over connection 334. Filters 316 may dothis by using standard HTTP methods, such as PUT commands, althoughother commands may be used. Again, data aggregator 310 may include otherfilters that route API messages/information to other destinations. As anexample, system 300 also may also include a data storage system 390 thatmay receive information from filters 316 and store this information in adatabase. Database 390 may be flat database, relational/SQL database,NoSQL/non SQL database, and/or a time series database, etc., althoughany form of database(s) may be used. One will appreciate that filters316 may communicate API messages to the web server 340 one at a time, orin batches on a periodic basis (such as every X seconds or minutes,every Y messages, and/or when Z bytes of messages are ready to beforwarded, etc.). Other variations are possible.

As noted above, pipe module 314 may be multiple message queues, eachhaving respective filters 316. Here, each filter 316 may have arespective connection 334 with web server 340 and may be similarlyconfigured to discard certain API messages received from its respectivemessage queue and to communicate the remaining API messages to the webserver 340 over its respective connection.

According to one specific example, one or more operations/functions ofdata aggregator 310 may be provided by Amazon Web Services, where APImessages from the message broker 370 may fed to a Kinesis Streamconsisting of one or more shards, and where Lambda function(s) mayobtain the API messages from the Kinesis Stream, filter the API messagesto discard certain messages, and forward the remaining API messages (andassociated topics) over HTTP interface(s) 334 to the web server 340.Other examples are possible.

Turning now to web server 340, it may be one or more computing devices(e.g., one or more computing servers) that may include one or moregeneral purpose processors, special purpose processors, conventionalprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, integrated circuits, programmable logic devices (PLD),field programmable gate arrays (FPGA), application specific integratedcircuits (ASICs), or any suitable controller or processing device or thelike (hereinafter collectively referred to as processor(s)) (not shown),for example. The processor(s) of web server 340 may be configured toexecute one or more software-based applications and/or firmware basedmodules that include instructions that when executed by the processor(s)may configure the processor(s) to perform signal coding, dataprocessing, input/output processing, or any other function thatconfigures the web server 270 to function/operate as described herein.One will also recognize that features, functions, and processesdescribed herein of the web server 270 may also and/or alternatively beprovided by hardware in addition to and/or as an alternative tosoftware-based instructions and processes. Web server 340 may alsoinclude one or more memory modules/devices (including volatile andnon-volatile memory modules/devices) that may be communicatively coupledto the processor(s). The memory modules/devices may be implemented asone or more external integrated circuits (IC) and/or as one or moreinternal circuits of the processor(s). The one or more memorymodules/devices may store the software-based applications and may alsoprovide an execution space as the processors execute applications. Webserver 340 may also include one or more communicationinterfaces/transceivers/network interface devices (not shown)communicatively coupled to the processors and/or memory devices/modules.The communication interfaces may allow web server 340 to communicateover one or more wired and/or wireless communication networks (notshown). Over these networks, web server 340 may support one or moreconnections 334 with the data aggregator 310, and may support respectiveconnections 336 and 338 with respective network devices 380. The webserver 340 may support HTTP/HTTPS based interfaces with standard methodson these connections, for example, to communicate with the dataaggregator 310 and network devices 380. In one aspect, web server 340may function as an HTTP publish-subscribe server.

Web server 340 may include a web service module 342 (also referred toherein as web service) and a worker service module 344 (also referred toherein as worker service) (One will recognize that the names web server,web service, and worker service as used herein are for descriptionpurposes only). Each of these modules may operate as one or moresoftware based processes within the web server. A message queue 348, forexample, may connect the web service module 342 and the worker servicemodule 344. This message queues may be implemented as a Redis cache,although other implementations may be used. Web server 310 may alsoinclude one or more databases such as subscription database 346.Subscription database 346 may be flat database, relational/SQL database,NoSQL/non SQL database, and/or a time series database, etc., althoughany form of database(s) may be used. While web server 340 is shown ashaving example modules 342 and 344, message queue 348, and database 346,the server may have other configurations.

Beginning with subscription database 346, it may include at least oneentry for each system controller 250 a and 250 b of system 300. Asfurther described below, web service 342 may treat/use the MAC addressesof the system controllers 250 a and 250 b as topics or channels (as thatterm may be used for an HTTP publish-subscribe server) that networkdevices 380 may subscribe to, although this is one example and otherexamples are possible. Assuming this format is used, the subscriptiondatabase 346 may include the MAC address for each system controller 250a and 250 b and may further include and associate/relate with each MACaddress the respective topics that the system controller publishesand/or subscribes to with the message broker 370. For example and ashown by callout 350, for system controller 250 a the subscriptiondatabase 346 may include the MAC address of the system controller(“A1:B1:C1:D1:E1:F1”), and may associate with this address one or moreof the topics used by the system controller 250 a (here,“/u/1202/d/ABC123/Request” and “/u/1202/d/ABC123/Response”). Similarly,for system controller 250 b the subscription database 346 may includethe MAC address of the system controller (“A2:B2:C2:D2:E2:F2”), and mayassociate with this address one or more of the topics used by the systemcontroller 250 b (“/u/1202/d/ABC789/Request” and“/u/1202/d/ABC789/Response”). A system administrator may configure andmaintain this database. Hence, as new user environments 202 withrespective system controllers 250 are added to system 300, thesubscription database 346 may be updated to include the MAC address andassociated topics of the new system controller. Again, this is oneexample and other examples are possible. As another variation, webservice 342 may treat/use the System-Controller-IDs of the systemcontrollers 250 a and 250 b as topics or channels that network devices380 may subscribe to. Assuming this format is used, the subscriptiondatabase 346 may include the System-Controller-ID for each systemcontroller 250 a and 250 b and may further include and associate/relatewith each System-Controller-ID one or more of the respective topics thatthe system controller publishes and/or subscribes to with the messagebroker 370. For example, the subscription database 346 may be configuredas follows:

System-Controller-ID: ABC123

-   -   Topic: /u/1202/d/ABC123/Request    -   Topic: /u/1202/d/ABC123/Response

System-Controller-ID: ABC789

-   -   Topic: /u/1202/d/ABC789/Request    -   Topic: /u/1202/d/ABC789/Response

Again, this is one example and the web service 342 may associate anyvalue/identifier with respective system controllers 250 a and 250 b anduse that value/identifier as a topic or channel, and associate thatvalue/identifier with one or more of the topics used by the systemcontrollers. For purposes of description, web service 342 will bedescribed herein as using the MAC addresses of the system controllers250 a and 250 b as topics/channels.

Turning to web service 342, as indicated it may treat each of the MACaddresses listed in the subscription database 346 as a topic or channelthat a network device 380 may subscribe to via interface 336. Web server340 may be configured to operate as follows. A network device 380 maydesire to receive API messages published by system controller 250 a, forexample, to the message broker 370. To do this, network device 380 maycommunicate with web service 342 via connection 336 to subscribe to theMAC address of system controller 250 a (i.e., subscribe to MAC address“A1:B1:C1:D1:E1:F1”). In subscribing to the MAC address with the webservice 342, network device 380 may also provide the web service with anotification address (e.g., a uniform resource locator (URL)) to whichthe web server 340 may post any API messages. The web service may storethis notification address in subscription database 346 together with anindication that the network device 380 has subscribed to the MAC addressof the system controller 250 a. In a similar fashion, the network device380 may also communicate with web service 342 via connection 336 tounsubscribe to a MAC address of a system controller, such as systemcontroller 250 a. In turn, the web service may update the subscriptiondatabase 346 to indicate that the network device 380 has unsubscribed tothe MAC address of the system controller 250 a. Web service 342 maystore which network devices 380 have subscribed to which channels inother manners.

According to one example, web service 342 may receive over connection(s)334 from the data aggregator 310 the API messages published by allsystem controllers 250 a and 250 b as described above (or a subsetthereof if the filters 316 have removed certain API messages such ascertain status messages). Again, these API messages may have topicsassociated with them of the form “/u/1202/d/ABC123/Response” and“/u/1202/d/ABC789/Response”, as an example. As the API messages arereceived, the web service 342 may translate the topics to MAC addressesusing the configuration information of the subscription database 346.For example, the web service 342 may translate the topic“/u/1202/d/ABC123/Response” of API messages from system controller 250 ato the MAC address “A1:B1:C1:D1:E1:F1” of system controller 250 a. Theweb service 342 may then determine whether any network device 380 hassubscribed to this MAC address. If a network device 380 has subscribedto the MAC address, the web service 342 may write, for example, the APImessage together with its associated topic and/or MAC address to themessage queue 348. On the contrary, if no network device 380 hassubscribed to the API message, the web service 342 may discard the APImessage. As an alternative to translating topics of API messagesreceived from the data aggregator 310 to MAC addresses as justdescribed, as a network device 380 subscribes to a MAC address the webservice 342 may use the subscription database 346 to translate the MACaddress to a topic or a portion thereof (e.g., translate the MAC address“A1:B1:C1:D1:E1:F1” of system controller 250 a to the topic“/u/1202/d/ABC123/Response”). As the web service receives from the dataaggregator 310 the API messages published by the system controllers 250a and 250 b, it may compare the topics associated with the messages to“topics” subscribed to by network devices 380. If a network device 380has subscribed to the topic, the web service 342 may write the APImessage together with its associated topic and/or MAC address to themessage queue 348. On the contrary, if no network device 380 hassubscribed to the API message, the web service 342 may discard the APImessage. Other variations are possible. In general, through a MACaddress as specified by a network device and through theSystem-Controller-ID portion of the topics associated with API messages,the web service, at least in part, may correlate/associate received APImessages to the messages the network devices are looking to receive.

As described above, web service 342 may receive from the data aggregator310 the API messages published by the system controllers 250 a and 250 b(or a subset thereof if the filters 316 have removed certain APImessages), and may then determine or analyze each API message todetermine whether any network device 380 has a subscription to receivethe respective API message. As another variation, as filters 316receives API messages from the pipe module 314, it may discard certainmessages (such as certain status messages), and then periodically batchthe remaining messages into blocks. How it batches messages into blocksmay vary. Some examples may include (i) batching messages on a timebasis (e.g., batch messages over X min periods), (ii) batching messageson a number of API messages (e.g., create blocks of X API messages),(iii) batching messages on a size basis (e.g., create blocks of X bytesor less), or some combination thereof. With respect to each batch of APImessages, filters 316 may determine the topics associated with themessages, and communicate a list of these topics to the web service 342over connection 334. For example, filters 316 may provide the fulltopics (e.g., “/u/1202/d/ABC123/Response” and“/u/1202/d/ABC789/Response”) or a just a portion of the topics (e.g.,just the System-Controller-IDs). As an alternative, filters 316 may haveaccess to subscription database 346 (as shown by connection 318) andtranslate topics to MAC addresses and pass MAC addresses to the webservice 342. Other examples are possible. Regardless, filters 316 maynot forward the actual API messages at this time. Upon receiving thelist of topics, web service 342 may determine for each topic whether anetwork device 380 is presently subscribed to the topic (e.g., bycorrelating topics with MAC addresses that have been subscribed to) andcommunicate back to filters 316 over connection 334 an indication ofthose topics that are subscribed to (or alternatively, not subscribedto). Upon receiving this communication from the web service 342, filters316 may discard from the batched API messages those that are notsubscribed to and forward the remaining API messages to the web service316 over connection 334. Upon receiving the API messages, the webservice 342 may write each API message together with its associatedtopic and/or MAC address to the message queue 348. Filters 316 and theweb service 342 may then repeat the process, with filters 316 batchinganother set of API messages and communicating with web service todetermine which associated topics are currently subscribed to. Othervariations are possible. One advantage of this configuration is thatless data needs to be communicated from the data aggregator 310 to theweb server 340, providing more efficient communications.

According to a still further variation, each time a network device 380subscribes with the web service 342 to a MAC address of a systemcontroller 250 for example, web service 342 may translate that MACaddress to a topic (e.g., for system controller 250 a, it may translatethe MAC address “A1:B1:C1:D1:E1:F1” to the topic“/u/1202/d/ABC123/Response”). Web service 342 may then communicate thetopic to the filters 316 over connection 334, instructing filters 316 toforward any API message having the corresponding topic. As analternative, assuming filters 316 have access to subscription database346 for example, web service 342 may pass MAC addresses to filters 316,which may then translate the MAC addresses to topics. Other examples arepossible. One will appreciate that if multiple network devices 380subscribe to API messages from the same system controller, web service342 may only communicate once with filters 316. Regardless, as filters316 receives API messages from pipe module 314, it may discard certainmessages (such as certain status messages), and then compare the topicsof the API message to the topics provided to it by the web service 342to determine whether a network device 380 has subscribed to receive themessage. If a network device 380 has subscribed to the topic, thefilters 316 may forward the API message (and it associated topic) to theweb service 342 over connection 334. Web service 342 may then write theAPI message together with its associated topic and/or MAC address to themessage queue 348. On the contrary, if no network device 380 hassubscribed to the API message, the filters 316 may discard the APImessage. Similarly, each time a network device 380 unsubscribes with theweb service 342 to a MAC address of a system controller 250, web service342 may translate that MAC address to a topic and then communicate thetopic to the filters 316 over connection 334, instructing filters 316 tostop forwarding related API messages. One will appreciate that ifmultiple network devices are subscribed to the same MAC address at thesame time, web service 342 may not communicate this instruction to thefilters 316 if other devices are still subscribed. Again, this is merelyan example and other variations are possible.

Turning to worker service 344, it may read API messages from the messagequeue 348, determine the notification address of each network device 380that subscribed to receive the API message, and use the notificationaddress to communicate the API message to the respective network deviceover a respective connection 338 (one will recognize that thenotification address may be different from the network device). Theworker service 344 may determine notification addresses using thesubscription database 346 as indicated above although other mechanismsmay be used to determine the addresses. In communicating the API messageto a network device, the worker service 344 may include the topicassociated with the API message and/or the MAC address of the respectivesystem controller. Thereafter, the network device 380 may receive andoperate on the API message, for example.

While the web service 342 and worker service 344 are shown and describedas communicating via message queue 348, this queue may not be requiredand the two modules may communicate in other fashions. In one aspect,however, message queue 348 may provide one mechanism of temporarilystoring API messages in high data demand situations. Also, the use ofMAC addresses, for example, rather than the noted “Request” and“Response” topics as a mechanism for network devices 380 to subscribe toAPI messages is not necessarily required and web service 342 and networkdevices 380 may be configured to subscribe to the noted topics directly(i.e., a network device 380 may subscribe to“/u/1202/d/ABC123/Response”). Nonetheless, the noted configuration ofusing MAC addresses or a variation thereof, for example, has at leastone benefit in that the system controllers 250 and subscription database346 may be updated at future times to use different topics. The networkdevices using MAC addresses (which may be static values), for example,that are correlated to the noted topics may allow topics to changewithout affecting service applications provided by network devices.

Again, a given network device 380 may subscribe to receive from webserver 340 API messages produced by numerous system controllers.Similarly, numerous different network devices may subscribe to receivefrom web server 340 API messages produced by the same system controller.

Turing now to FIG. 4, there is shown an example system 400. System 400may be similar to system 300 but in addition to receiving API messagesfrom system controllers 250 a and 250 b, network devices 380 may alsocommunicate API messages to designated system controllers 250 a and 250b (such as to control light levels in a respective user environments)using an HTTP interface, for example.

According to system 400, web server 340 may now also include an MQTTclient module 472 that may support a communications connection 474 withthe message broker 370. This connection may be, for example, a TCP/IPbased connection, although other connections may be used. On top of thisconnection the MQTT client 472 may support the MQTTpublish-subscribe-based messaging protocol with the message broker 370,with the MQTT client 472 acting as a client to the message broker, forexample. As the MQTT client 472 of the web server 340 establishesconnection 474 with the message broker and forms an MQTT connection tothe broker, the message broker may start a respective process 476 withthe MQTT client 472, for example.

To communicate an API message to a specific system controller 250, suchas system controller 250 a, a network device 380 may publish the APImessage over connection 336 to the web service 342 and in particular,may publish the message to the MAC address of system controller 250 a(i.e., “A1:B1:C1:D1:E1:F1”). Noting that the network device haspublished the API message to the MAC address, web service 342 may usesubscription database 346 to translate the MAC address to the “Request”topic associated with the MAC address (here,“/u/1202/d/ABC123/Request”). Thereafter, the web service may forward theAPI message and the “/u/1202/d/ABC123/Request” topic, for example, tothe MQTT client 472. MQTT client 472 may in turn publish the API messageover connection 474 to the message broker 370 using the topic“/u/1201/d/ABC123/Request”. At the same time, MQTT client 472 may alsosubscribe over connection 474 with the message broker 370 to the“Response” topic associated with the MAC address of controller 250 a(i.e., “/u/1202/d/ABC123/Response”), which may also be forwarded by theweb service 342 to MQTT client 472, for example. By subscribing to the“Response” topic of system controller 250 a, MQTT client 472 may receivefrom the system controller 250 a any response to the API message.

Accordingly, as process 476 receives the API message from MQTT client472, the message broker 370 may forward the API message to process 272 afor forwarding to the system controller 250 a (the controller 250 ahaving subscribed to the topic “/u/1202/d/ABC123/Request” as discussedabove). As the system controller 250 a processes the API message, it maygenerate a response API message, which it may publish to the messagebroker 370 using topic “/u/1202/d/ABC123/Response”, as described forsystem 200 and 300, for example. Because the MQTT client 472 subscribesto the topic “/u/1202/d/ABC123/Response”, the message broker 370 mayforward this response API message from process 272 a to process 476,which may then forward the response API message to MQTT client 472 overconnection 474. Upon receiving, for example, the response API message,MQTT client 472 may unsubscribe to the topic“/u/1202/d/ABC123/Response”, and may forward the response API message tothe web service 342. Web service 342 may thereafter translate the topicof the response API message from “/u/1202/d/ABC123/Response” back to theMAC address of the system controller 250 a, and communicate the responseAPI message to the network device 380 over connection 336. Again, othervariations are possible, such as the network device 380 subscribing tothe System-Controller-IDs rather than MAC addresses, for example.

According to a further aspect of system 400, web server 340 may have aplurality (two or more) of MQTT clients 472 with respective connections474 to the message broker 370. The web service 342 may use respectiveones of the MQTT clients 472, one at a time, to communicate API messagesfrom network devices 380 to respective system controllers 250 and toreceive responses thereto.

While system 400 is described herein as being based on the MQTTprotocol, other message based protocols may be used, such as theAdvanced Message Queuing Protocol (AMQP).

While system 300 and system 400 are described herein as including dataaggregator 310, another variation of these systems may not include thismodule. Here, the message broker 370 may directly communicate APImessages to the web server 340. Data aggregator 310 may not be needed,for example, if the message broker 370 is receiving a limited amount ofinformation from the load control systems 210 a and 210 b, and/or ifthere is a limited number of load control systems providing informationto the message broker. Similarly, variations of system 300 and system400 may include data aggregator 310, but may not necessarily includefilters 316 that are configured to remove API messages from the streamof API messages from pipe module 314. In other words, data aggregator310 may forward all API messages to the web server 340 that it receivesfrom the message broker rather than removing some messages. Nonetheless,one will recognize that the data aggregator and its respective filtersmodule may provide one example mechanism for controlling the rate atwhich information flows into the web server 340 and the amount of datathat flows into and needs to be communicated to the web server. Inaddition, while the system controllers 250 a and 250 b have beendescribed herein as generally forwarding, in a non-selective fashion,large amounts of information/API messages to the message broker with thedata aggregator then filtering this information, the system controllersmay be configured to selectively forward only certain API messages tothe message broker. However, this may not be desirable in that if it islater realized that other information may be needed/wanted from thesystem controllers, it may be difficult to access all of these systemsand make the modification. The system controllers non-selectivelyforwarding large amounts of information/API messages to the messagebroker and the filters module 316 being configured to selectivelydiscard certain API messages has one advantage in that if it is laterrealized that it may be desirable to have the filters 316 forwardadditional information or discard other information, an administratormay simply update the filters.

Turning now to FIG. 5, there is shown an example system 500. System 500is similar to system 400, for example, but may now also allow a networkdevice 580 to communicate messages with (i.e., send messages to andreceive messages from) designated system controllers 250 a and 250 busing an API that is different from the API supported by the systemcontrollers. In other words, as discussed with respect to system 400, anetwork device 380 may communicate with system 400 using the APIsupported by the system controllers 250 a and 250 b. According to system500, network device 580 may communicate over an HTTP interface withsystem 500 but now use a third-party API that may be specific to thenetwork device, with system 500 translating between the API supported bythe system controllers and the third-party API. For description purposesonly, messages formatted according to the API supported by the systemcontrollers 250 a and 250 b will be referred to herein as “APImessages”, and messages formatted according to the third-party APIsupported by the network controller 580 will be referred to herein as“third-party API messages”.

Network device 580 may be similar to network devices 280 a and 280 b andnetwork device 380 in that it may be a device in use by a user (e.g., ahome-owner of a user environment) and/or may be a third-party integratorconfigured to provide a service(s) based on interactions with respectivesystem controllers 250 a and 250 b. While FIG. 5 shows only one networkdevice 580, there may be numerous such devices each configured tocommunicate with one or more system controllers, possibly at the sametime.

As compared to system 400, data aggregator 310 of system 500 may nowinclude a gateway module 502 (also referred to herein as gateway) and anAPI translator module 504 (also referred to herein as API translator)(One will recognize that the names gateway and API translator as usedherein are for description purposes only). While gateway module 502 andAPI translator module 504 are shown as being part of data aggregator310, these modules may alternatively be provided by one or more othercomputing devices such as by web server 340 or message broker 370, forexample, or by another computing device(s) separate from any of messagebroker 370, data aggregator 310, or web server 340. Each of gatewaymodule 502 and API translator module 504 may operate as one or moresoftware based processes within the data aggregator, although otherimplementations are possible

Beginning with gateway 502, it may be configured to support respectivenetwork communication connections 508 with network device 580 for eachsystem controller 250 a and 250 b the network device is communicatingwith. Gateway 502 may support an HTTP/HTTPS based interface onconnection 508 that may be used by network device 580 to communicatewith gateway 502. As indicated, services provided by network device 580may be based on a third-party API. As such, network device 580 maycommunicate to gateway 502 a third-party API message for a particularsystem controller 250 a and 250 b. Gateway 502 may be configured to thenforward that third-party API message to the system controller as furtherdescribed below. Similarly, if the system controller responds with anAPI message, that response message may be forwarded to the gateway 502,which may then forward the response message to the network device as athird-party API message. Similarly, network device 580 may communicatewith gateway 502 to subscribe to receive API messages published by aparticular system controller 250 a and 250 b. Gateway 502 may beconfigured to forward this subscription request to the web server 340.As the web server receives API messages from a subscribed to systemcontroller, the web server may forward these messages to the gateway502, which may then forward the message to the network device asthird-party API messages. According to one example, gateway 502 may beagnostic to the specific third-party API used by network device 580, butmay be configured such that the format of the third-party API used bythe network device needs to be based on a standard. As one example,gateway 502 may be configured such that the third-party API may need tobe a RESTful (representational state transfer) based API where, forexample, network device 580 communicates with gateway 502 using standardmethods (such as, for example, GET, PUT, POST, DELETE, etc.) and where,for example, system controllers 250 a and 250 b and control devices 220a and 220 b, for example, are treated as resources. Again, this is oneexample and others are possible.

Turning to API translator 504, it may provide API translation servicesfor system 500. In particular, API translator 504 may have a connection510 with gateway 502. As gateway 502 receives a third-party API messagefrom network device 580 that is destined for a particular systemcontroller 250 a or 250 b, the gateway may forward that message to APItranslator 504. API translator 504 may be configured to then translatethe third-party API message to an API message (i.e., API messagesupported by the system controllers) and forward the API message to thesystem controller. Similarly, assuming the system controller respondswith an API message, that message may be forwarded to the API translator504. The API translator 504 may be configured to then translate the APImessage to a third-party API message and forward the third-party APImessage to the gateway 502, which may then forward the message to thenetwork device 580. Similarly, as gateway 502 receives from networkdevice 580 a subscription request to receive API messages published by aparticular system controller, such as system controller 250 a, thegateway may forward that request to the web server, possibly through theAPI translator 504 for translation, if necessary. Assuming the webserver receives at connection 334 API message(s) published by systemcontroller 250 a, the web server may forward those API message(s) to theAPI translator 504. The API translator 504 may be configured to thentranslate the API message(s) to third-party API message(s) and forwardthe third-party API message(s) to the gateway 502, which may thenforward the message(s) to the network device 580.

According to one example, system 500 may include multiple APItranslators 504, each configured to translate messages between the APIused by the system controllers and the third-party API used by thenetwork device, and each having a respective connection 510 with gateway502. As network device 580 desires to communicate with and/or receivemessages from a particular system controller 250 a or 250 b, gateway 504may use an “available” API translator 504 for that communication. Inother words, a given API translator 504 may only support communicationswith a one system controller 250 a and 250 b at any given time.According, to one example, API translators 504 may statically exist(i.e., there is a defined number “running” or executing at any giventime) and available/free translators may be used by gateway 502 asneeded. According to another example, API translators may be created asneeded by the gateway 502. According to this example, gateway 502 andAPI translator(s) 504 may be specific to a particular third-party API.As discussed below, additional instances of gateway 502 and APItranslator(s) 504 may be used to support additional third-party APIs.

Assuming system 500 includes multiple API translators 504, as furthershown in FIG. 5 each API translator may have a respective communicationsconnection 512 with web server 340 and in particular, with web service342. This connection may be, for example, a TCP/IP or UDP/IP basedconnection, although other connections may be used. Web server 340/webservice 342 may support an HTTP/HTTPS based interface on this connectionwith standard methods as discussed herein.

Reference will now be made to an example operation of system 500. Tocommunicate a particular command or request, for example, to a specificsystem controller 250, such as system controller 250 a, network device580 may communicate a third-party API message to the gateway 502 viacommunications connection 508. The network device may communicate themessage using a standard POST command, for example. With thisthird-party API message, the network device may include the MAC addressof system controller 250 a (i.e., “A1:B1:C1:D1:E1:F1”) (although theSystem Controller Unique ID Value may also be used, for example). Uponreceiving the message, the gateway 502 may forward the third-party APImessage (and MAC address) to a respective API translator 504 via arespective connection 510. Upon receiving the message, the APItranslator 504 may translate the third-party API message to an APImessage. Thereafter, the operation flow may proceed as similarlydiscussed with respect to FIG. 4, for example. The API translator 504may next publish the API message over a respective connection 512 to theweb service 342 and in particular, may publish the message to the MACaddress of system controller 250 a (i.e., “A1:B1:C1:D1:E1:F1”). Notingthat the API translator has published the API message to the MACaddress, web service 342 may use subscription database 346 to translatethe MAC address to the “Request” topic associated with the MAC address(here, “/u/1202/d/ABC123/Request”). Thereafter, the web service mayforward the API message and the “/u/1202/d/ABC123/Request” topic to theMQTT client 472. MQTT client 472 may in turn publish the API messageover connection 474 to the message broker 370 using the topic“/u/1201/d/ABC123/Request”. At the same time, MQTT client 472 may alsosubscribe over connection 474 with the message broker 370 to the“Response” topic associated with the MAC address of controller 250 a(i.e., “/u/1202/d/ABC123/Response”). By subscribing to the “Response”topic of system controller 250 a, MQTT client 472 may receive from thesystem controller 250 a any response to the API message.

Accordingly, as process 476 of the message broker 370 receives the APImessage from MQTT client 472, the message broker may forward the APImessage to process 272 a for forwarding to the system controller 250 a(the controller 250 a having subscribed to the topic“/u/1202/d/ABC123/Request” as discussed above). As the system controller250 a processes the API message, it may generate a response API message,which it may publish to the message broker 370 using topic“/u/1202/d/ABC123/Response”, as described for system 200, 300, and 400for example. Because the MQTT client 472 subscribes to the topic“/u/1202/d/ABC123/Response”, the message broker 370 may forward thisresponse API message from process 272 a to process 476, which may thenforward the response API message to MQTT client 472 over connection 474.Upon receiving the response API message, MQTT client 472 may unsubscribeto the topic “/u/1202/d/ABC123/Response”, and may forward the responseAPI message to the web service 342. Web service 342 may thereaftertranslate the topic of the response API message from“/u/1202/d/ABC123/Response” back to the MAC address of the systemcontroller 250 a, and communicate the response API message to the APItranslator 504 over connection 512.

Upon receiving the API response message from the web service 342, APItranslator 504 may translate the API message to a third-party APImessage (such as a response message) and forward the third-party APImessage over connection 510 to gateway 502. Thereafter, gateway 502 mayforward the third-party API message to network device 580. Again, othervariations are possible.

Similarly, for network device 580 to subscribe to receive API messagespublished by a system controller, such as system controller 250 a,network device 580 may communicate with gateway 502 via communicationsconnection 508 to subscribe to the MAC address of system controller 250a, for example. Upon receiving the subscription request, the gateway 502may forward the request to a respective API translator 504 via arespective connection 510, which may then forward the request over arespective connection 512 to the web service 342, translating therequest if necessary. Alternatively, the gateway 502 may forward thesubscription request directly to the web service. Regardless, theoperation flow may then proceed as similarly discussed with respect toFIG. 3, for example. As the web service 342 receives via connection 334from data aggregator 310 API messages published by system controller 250a, the web service may determine that a network device, such as networkdevice 580, has subscribed to receive these API messages as discussedherein. The web service 342 may in turn then forward these API messages(together with its associated topic and/or MAC address, for example) toa respective API translator 504 via a respective connection 510.Alternatively, the web service 342 may forward these API messages to theworker service 344 (such as through message queue 348), which may inturn forward the API messages (together with its associated topic and/orMAC address, for example) to a respective API translator 504 via arespective connection 510. Other variations are possible. Upon receivingan API message from the web service 342, API translator 504 maytranslate the API message to a third-party API message and forward thethird-party API message over a respective connection 510 to gateway 502.Thereafter, gateway 502 may forward the third-party API message tonetwork device 580. In communicating the third-party API message to anetwork device, the message may include the topic associated with theAPI message and/or the MAC address of the respective system controller250 a. Again, other variations are possible.

As indicated above, according to the example shown in FIG. 5 gateway 502and API translator(s) 504 may be specific to a particular third-partyAPI. According to a further aspect of system 500, the system may supportmultiple different third-party APIs. Here, system 500 may includemultiple instances/pairs of gateway 502 and API translator(s) 504, witheach gateway/API translator(s) pair supporting a respective third-partyAPI. Depending on which API is used by a network device 580, the devicemay communicate with a corresponding gateway (e.g., each gateway mayhave a respective address/URL to which the network device communicates).

According to one specific example, one or more of gateway 502 and APItranslator(s) 502 may be provided by Amazon Web Services, where gateway502 may be an Amazon API Gateway, and where each respective instance ofan API translator may be a respective Lambda function configured toperform API translation as discussed herein and to communicate with webserver 340 as discussed herein. Here, the Amazon API Gateway may exposeendpoints to network devices 580, and Lambda functions that areconfigured as described herein may be assigned to respective gatewayendpoints.

Referring now to a still further aspect of systems 300, 400, and 500, asdiscussed herein web server 340 may treat/use the MAC address, forexample, of the system controllers 250 a and 250 b as topics or channelsthat network devices 380 and 580 may subscribe to, and/or publishmessages to, for example. The subscription database 346 may include theMAC address of the system controllers, and may associate with thisaddress one or more of the topics used by the system controllers 250 aand 250 b, as shown by callout 350. Again, this is one example.

According to a further example, authorization/access tokens may also beassociated with respective system controllers 250 a and 250 b, and thesetokens then associated with one or more of the topics used by the systemcontrollers, with systems 300, 400, and 500 using the tokens in asimilar way as to how MAC addresses may be used as described herein. Forexample, for security purposes in order for a network device 380 or 580(i.e., third-party) to communicate with web server 340 or gateway 502 togain access to a user environment 202 a or 202 b/load control system 210a or 210 b, the network device may need to include with the HTTPmessages, for example, an authorization/access token that can be used byweb server 340 and/or gateway 502 to ensure the network device ispermitted access to a user environment 202 a or 202 b/load controlsystem 210 a or 210 b. A user (such as a homeowner) of the userenvironments/load control systems may obtain such tokens using, forexample, an OAuth (e.g., OAuth 2.0) based service. Such a service may beprovided separate from systems 300, 400, and 500. In the process of theuser obtaining such a token, it may be stored in the subscriptiondatabase 346, for example, and also provided to the third-party and usedby the third-party and the web server 340 and/or gateway 502 forauthentication/authorization purposes.

In this aspect, authorization tokens may be viewed as being associatedwith users. According to an aspect of systems 300, 400, and 500 thesetokens may also be associated with system controllers. For example,assume that a user/homeowner of user environment 202 a obtains a token“XYZ123” through an OAuth based service and assume that a user/homeownerof user environment 202 b obtain a token “XYZ456” through an OAuth basedservice. In addition to using these tokens for security purposes, thesetokens may be stored, for example, in the subscription database 346 (oralternatively, stored in another database such as an authorizationdatabase with database 346 having links to the tokens as stored in theauthorization database) and associated with the respective systemcontrollers 250 a and 250 b and thus associated with one or more of thetopics used by the system controllers, as shown in callout 350 of FIG.5.

As discussed with respect to system 300 of FIG. 3, in order for anetwork device 380 to receive API messages published by systemcontroller 250 a, for example, it may subscribe to MAC address“A1:B1:C1:D1:E1:F1” as discussed herein. With respect to authorizationtokens, as the network device 380 communicates an HTTP message to theweb server 340 to subscribe to receive API messages from systemcontroller 250 a, the web server 340 may treat/use the authorizationtoken within the HTTP message (i.e., “XYZ123”) as a request to subscribeto the authorization token, with system 300 now using the token in asimilar way to how it used MAC addresses in order to determine that APImessages published by the system controller 250 a should be forwarded tothe network device.

Similarly, as discussed with respect to system 400 of FIG. 4, in orderfor a network device 380 to communicate an API message to systemcontroller 250 a, for example, it may publish the message to the MACaddress of the system controller. With respect to authorization tokens,as the network device communicates an HTTP message to the web server topublish an API message to the system controller 250 a, the web server340 may treat/use the authorization token within the HTTP message (i.e.,“XYZ123”) as a request to publish the API message to the authorizationtoken, with system 400 now using the token in a similar way to how itused MAC addresses in order to communicate API messages with the systemcontroller 250 a.

Similarly, as discussed with respect to system 500 of FIG. 5, in orderfor a network device 580 to communicate a third-party API message tosystem controller 250 a, for example, it may communicate the MAC addressof the system controller to the gateway 502. With respect toauthorization tokens, as the network device 580 communicates an HTTPmessage (that includes the third-party API message) to the gateway, thegateway may forward the authorization token from the HTTP message (i.e.,“XYZ123”) to the API translator 504, which may translate the third-partyAPI message to an API message. As the API translator 504 communicates anHTTP message to the web server 340 to publish the API message to thesystem controller 250 a, it may include the token with the HTTP message(e.g., for authorization purposes). The web server 340 may thereaftertreat/use the authorization token within the HTTP message (i.e.,“XYZ123”) as a request to publish the API message to the authorizationtoken, with system 500 now using the token in a similar way to how itused MAC addresses in order to communicate API messages with the systemcontroller 250 a. Authorization tokens may also be used in a similarfashion in system 500 for a network device 580 to subscribe to receiveAPI message published by a system controller. Again, other exampleprocess flows are possible.

In general, one will recognize that functions and operations describedherein as the message broker 370, data aggregator 310, and web server340 may each be performed on different computing devices or the samecomputing device or some combination thereof. One or more of thesemodules may also be cloud based systems. Similarly, one will recognizethat functions and operations described herein as being performed by themessage broker 370, data aggregator 310, or web server 340 may beperformed by the other modules. For example, web server 340 may providefilters 316 rather than the data aggregator 310. Furthermore, whilefunctions and operations are described herein as being performed by themessage broker 370, data aggregator 310, and web server 340, functionsand operations may be performed by additional modules. For example, theweb service 342 and the worker service 344 may be distributed acrossmultiple computing devices. Subscription database 346 may be a databasemanagement system separate from the web server 340, etc. Othervariations are possible.

With reference now to FIGS. 6A-V an example control application 1103(FIG. 12) is now described that may execute at least in part on anetwork device 680. Network device 680 may be similar to any of networkdevices 144, 280 a-280 b, 380, and 580 as described herein and may be apersonal computer (PC), a laptop, a tablet, a smart phone, or equivalentdevice, for example, although it may also be another type of computingdevice. The control application may be a graphical user interface (GUI)based application that may provide a GUI based interface/GUI based“window(s)” to a user via the network device 680 and that may allow auser of the network device to interact with, control, and/or configurecontrol devices within a user environment (such as control devices 220 aof user environment 202 a). For description purposes only, load controlsystem 210 a of user environment 202 a and the communication systemsdescribed with respect to FIG. 2-FIG. 5 will be used herein as anexample load control system and communication system to describe thecontrol application. Nonetheless, the features and functions of thecontrol application 1103 described herein are applicable to other typesof control devices, load control systems, and communication systems. Asan example, the user environment 202 a may be a residence or home andthe user of the network device 680 may a residence of the home.Nonetheless, the example control application may be also applicable toother types of user environments such as a building, hotel, etc.

FIG. 12 shows an example block diagram of network device 680 (thisdiagram may also apply to any of network devices 144, 280 a-280 b, 380,and 580, for example). Network device 680 may include one or moregeneral purpose processors, special purpose processors, conventionalprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, integrated circuits, programmable logic devices (PLD),application specific integrated circuits (ASICs), or the like and/or mayfurther include other processing element(s) such as one or more graphicprocessors (hereinafter collectively referred to as processor(s) 1102).Processor(s) 1102 may control the functionality of the network deviceand may execute the control application 1103, in addition to othersoftware applications such an operating system(s), database managementsystems, etc., to provide features and functions as describe herein. Theprocessor(s) 1102 may also perform signal coding, data processing, powercontrol, input/output processing, and any other functionality thatenables the network device 680 to perform as described herein. Thenetwork device 680 may also include one or more memory modules/devices1104 (including volatile and non-volatile memory modules/devices) whichmay be non-removable memory modules/devices and/or a removable memorymodules/devices. Memory modules/devices 1104 may be communicativelycoupled to the processor(s) 1102. Non-removable memory modules/devices1104 may include random-access memory (RAM), read-only memory (ROM), ahard disk(s), or any other type of non-removable memory storage.Removable memory modules/devices 1104 may include a subscriber identitymodule (SIM) card, a memory stick, a memory card, or any other type ofremovable memory. The one or more memory modules/devices 1104 may storethe control application 1103 and may also provide an execution space asthe processor(s) execute the control application. Network device 680 mayalso include a visual display screen(s)/terminal(s) 1106 that may becommunicatively coupled to the processor(s) 1102. Together withprocessor(s) 1102, visual display screen(s) 1106 may display informationto the user via one or more GUI based interfaces/GUI based “window( )”as described herein. The display screen(s) 1106 and the processor(s)1102 may be in two-way communication, as the display screen 1106 mayinclude a touch sensitive visual screen module configured to receiveinformation from a user and providing such information to theprocessor(s) 1102 Network device 680 may also include one or moreinput/output (I/O) devices 1112 (e.g., a keyboard, a touch sensitivepad, a mouse, a trackball, audio speaker, audio receiver, etc.) that maybe communicatively coupled to the processor(s) 1102. The I/O devices mayallow the user to interact with the control application 1103, forexample. Network device 680 may further include one or moretransceivers/communications circuits (collectively, communicationscircuit(s) 1108) for communicating (transmitting and/or receiving) overwired and/or wireless communication networks, for example. Thecommunications circuit(s) 1108 may include an RF transceiver(s) or othercircuit(s) configured to perform wireless communications via anantenna(s). Communications circuit(s) 1108 may be in communication withprocessor(s) 1102 for transmitting and/or receiving information. Each ofthe modules within the network device 680 may be powered by a powersource 1110. The power source 1110 may include an AC power supply and/orDC power supply, for example. The power source 1110 may generate asupply voltage V_(CC) for powering the modules within the network device680.

In addition to including GUI based software modules, for example, thatprovide the graphical features and visual images described herein, thecontrol application 1103 may also include a logic engine(s) forproviding features of the GUI and features of the application in generalas described herein. The GUI based software modules and/or logic enginemay be one or more software based modules that include instructions, forexample, that are stored on and/or execute from one or more tangiblememory devices/modules of the network device as indicated above.Features of the control application may also and/or alternatively beprovided by firmware and/or hardware in addition to/as an alternative tosoftware based modules. Again, network device 680 is an example and thecontrol application may execute on other types of computing devices.

As indicted, network device 680 may be similar to any of network devices144, 280 a-280 b, 380, and 580 as described herein. Accordingly, thecontrol application may communicate with system controller 250 a of theuser environment 202 a via a network local to the user environment (suchas a Wi-Fi network) similar to device 144 as described herein, maycommunicate with system controller 250 a using a message based protocol(e.g., MQTT) and a message broker (e.g., message broker 270) similar tonetwork devices 280 a-280 b as described herein, and/or may communicatewith system controller 250 a using an HTTP based interface similar tonetwork device 380 and/or network device 580 as described herein.Nonetheless, one will recognize that the control application1103/network device 680 may communicate with system controller 250 ausing other communication systems and/or protocols, etc. In addition,the control application 1103 is described herein as being aself-contained application that executes on the network device andcommunicates messages with the system controller 250 a, for example. Inother words, logic of the control application and generated graphicsassociated with the application are described herein as executing fromthe network device. Nonetheless, features and/or graphics of the controlapplication may be implemented in other fashions, such as a web hostedapplication with the network device interfacing with the web hostedapplication using a local application (e.g., a web browser or otherapplication) for providing features and functions as described herein.

In general, while user environment 202 a may include control devices 220a that the control application/network device 680 may interact with,control, and/or configure via system controller 250 a, the userenvironment may also include other types of control devices that may be,for example, Wi-Fi enabled and/or HomeKit enabled control devices forexample (e.g., devices that are configured to communicate via wirelessand/or wired based networks). For description purposes only, such othercontrol devices (i.e., control devices to which the controlapplication/network device 680 does not communicate with via the systemcontroller) will be referred to herein as Wi-Fi enabled and/or HomeKitenabled control devices. Nonetheless, one will recognize that thefeatures described herein are not limited to only Wi-Fi enabled and/orHomeKit enabled control devices. Examples of such other control devicesmay include lighting control devices/bulbs, thermostats, fans, etc.Network device 680 and these Wi-Fi enabled control devices, for example,may be configured to directly communicate with each other without havingto communicate through system controller 250 a (e.g., if the networkdevice is also HomeKit enabled), and/or may communicate via one or morecloud based servers, for example, again without communicating throughsystem controller 250 a. According to one aspect of the controlapplication 1103 described herein, assuming the network device isconfigured to communicate with such Wi-Fi enabled control devices (e.g.,via HomeKit), for example, the control application may be configured toalso interact with, control, and/or configure these devices, in additionto control devices 220 a. In so doing, the control application maycombine within the graphical interfaces described herein informationobtained from such Wi-Fi enabled devices, for example, and informationobtained on control devices 220 a that are controlled by the systemcontroller 250 a. The control application may also provide interfacesthat allow a user to control both Wi-Fi enabled control devices, forexample, and control devices 220 a that are controlled by the systemcontroller. For ease of description, the control application will bedescribed herein as interacting with control devices 220 a of loadcontrol system 210 a. Nonetheless, similar functionality as describedherein may also apply to Wi-Fi enabled devices that are not controlledvia the system controller 250 a and to which the network device maydirectly and/or indirectly communicate with. Which types of devices thecontrol application is interacting with may not be readily apparent tothe user. One will also recognize that the control application describedherein may alternatively only control Wi-Fi enabled devices, forexample, that the network device is configured to directly and/orindirectly control/interact with. Again, one will further recognize thatwhile control application 1103 is described herein in the context ofload control system 210 a and communication systems such as thosedescribed in reference to FIG. 2-FIG. 5, the features and functions ofthe control application are applicable to other types of controldevices, load control systems, and communication systems including forexample, Wi-Fi enabled and/or HomeKit enabled systems

As one example, the network device 680 may display to a user via avisual display screen an icon associated with the control application.The network device may detect the selection of the icon by the user(such as detecting the using touching the icon) and in response, maystart (which may also be referred to herein as launching, running,executing, activating and/or invoking) the control application (One willrecognize that the control application may be started in other ways,including the network device being configured to automatically start theapplication upon being reset and/or powered on). In response to beingstarted or launched, the control application (in addition to performingsecurity/authentication procedures, for example) may communicate one ormore messages to the system controller 250 a, for example, toobtain/request/query for various information, such as status/stateand/or configuration information of the load control system 210 a, anduse this information to initially generate and display to the user viathe display screen of the network device 680 a graphical user interface,such as interface 610 of FIG. 6A. Again, at starting, for example, thecontrol application may also communicate with Wi-Fi enabled devices, forexample, the network devices has been configured to communicate with.Thereafter, the control application may continue to request and/orreceive various information from the system controller 250 a at varioustimes depending on what information the control application may need todisplay to the user and/or is being generated by the system controller.(Again, the control application may also communicate with Wi-Fi enableddevices in a similar fashion.) Upon receiving information requests fromthe control application (such as requests for status and configurationinformation), system controller 250 a may respond by communicating withcontrol devices 210 a and/or database 254, for example, to determine andprovide the requested information and respond to the control applicationwith one or more response messages. In addition to determining statusand configuration of the load control system, for example, the controlapplication may also allow a user to communicate messages to the systemcontroller 250 a to modify, edit or change the configuration and/orstate of the load control system 250 a as further described herein. Inaddition, the system controller 250 a may also asynchronously providestatus and configuration information to the control application (e.g.,provide an indication of status/state changes of control devices withoutthe control application querying for such changes). The controlapplication may use this information to update various graphical userinterfaces displayed to the user via the network device 680. (Again,Wi-Fi enabled devices and the control application/network device mayinteract in similar fashions). Again, the control application/networkdevice 680 and system controller 250 a may communicate using mechanismsas discussed above with reference to FIGS. 2-5.

Before turning to various graphical user interfaces the controlapplication may provide to a user, a description of example types ofinformation the control application may request/receive from the systemcontroller 250 a, for example, to generate interfaces is firstdiscussed. One will recognize that these are examples and other types ofinformation may be provided. In addition to receiving such informationfrom the system controller, the control application may also alter suchinformation at the system controller, as described below.

The control application may request/obtain from the system controller250 a information related to the configuration and current state/statusof load control system 210 a. Such information provided by the systemcontroller 250 a may include the specific control devices that are partof the load control system 210 a including an identifier that indicatesthe type of the control device The specific control device types mayinclude one or more lighting control devices (referred to herein also aslighting devices) that each directly controls one or more respectiveelectrical lighting loads/lights, one or more temperature controldevices (such as and hereinafter also referred to as a thermostatdevice(s)) that directly control respective HVAC systems, one or moreceiling fan devices (also referred to herein as fan devices) that eachdirectly controls one or more respective fans (e.g., on, off, fanspeed), one or more audio control devices (e.g., a speaker system), andone or more window shade devices that each directly controls positionsor levels of one or more respective shades (One will recognize thatwhile shade devices and shades are discussed herein as an example ofmotorized window treatments and window covering, other types ofmotorized window treatments and window coverings are possible such asdrapes, curtains, blinds, etc.). The control devices may also includeone or more keypads, such as wall-mounted keypads, tabletop keypads,and/or remote-control/handheld keypads and devices. As an example, agiven keypad may include one or more actuators such as buttons (althoughother types of actuators are possible), and may be configured to controlone or more control devices/electrical loads (e.g., lighting controldevices/lighting load(s), HVAC system(s), shade(s), fan(s), and/orspeaker(s), etc.). In general, a keypad may include different types ofactuators such as on/off actuators, raise lower actuators for lights orshades, fan speed actuators, scene actuators, etc. A scene actuator mayset one or more control devices/electrical loads controlled by thekeypad to a pre-set configuration.

The control devices may also include one or more occupancy/vacancysensors and/or one or more vacancy only sensors. As an example, anoccupancy/vacancy sensor may signal to other control devices a detectedoccupancy event/condition and a detected vacancy event/condition (e.g.,after detecting an occupancy event). The sensor may signal these eventsby generating an occupancy signal(s)/message(s) when the sensor detectsan occupancy event, by generating periodic occupancysignal(s)/message(s) as it detects a continued occupancy event, and/orby generating vacancy signal(s)/message(s) when it detects a vacancyevent (e.g., after detecting an occupancy event). As another example, itmay signal a vacancy event by ceasing to generate periodic occupancysignal(s)/message(s). A vacancy only sensor may signal to other controldevices a detected vacancy event/condition (e.g., after detecting anoccupancy event). It may signal these events by generating vacancysignal(s)/message(s) when it detects a vacancy event (e.g., afterdetecting an occupancy event). In this example, the sensor may stillgenerate a signal(s)/message(s) when it detects an occupancy event, butcontrol devices may not be responsive to such signals. As anotherexample, a vacancy only sensor may signal a vacancy event by ceasing togenerate periodic occupancy signal(s)/message(s). One will recognizethat these are examples and sensors may operate in other ways based ondetected occupancy/vacancy events. One will also recognize that when asensor detects an occupancy and/or vacancy event, it may communicatethese events in various ways such as communicating signals or messages,etc. Such signals etc. may be communicated via wireless communications,wired communications, optical communications, etc. Other examples arepossible. For ease of description, occupancy/vacancy sensors and vacancyonly sensors are referred to herein collectively as occupancy sensorsand a sensor is referred to as generating signals when detectingoccupancy and/or vacancy events.

Load control system 210 a may be configured such that one or morecontrol devices 220 a may be responsive to the signals from a givenoccupancy sensor (e.g., be responsive to occupancy and/or vacancy eventsdetected by the sensor). For example, load control system 210 a may beconfigured such that one or more lighting control devices may beresponsive to occupancy and vacancy signals from a given occupancysensor. For example, in response to an occupancy signal from anoccupancy sensor, a given lighting control device that is off (i.e., itsrespective lighting load(s) are in an off state) may turn its respectivelighting load(s) on and in particular, may set the lighting load(s) to adefined lighting/dimming level(s). In response to a vacancy signal, thegiven lighting control device, when on, may turn its respective lightingload(s) off or may reduce their lighting level(s) to a definedlighting/dimming level(s). As another example, load control system 210 amay be configured such that one or more lighting control devices may beresponsive only to occupancy signals from a given occupancy sensor. As afurther example, load control system 210 a may be configured such thatone or more lighting control devices may be responsive only to vacancysignals from a given occupancy sensor. For example, in response to anoccupancy signal from an occupancy sensor, a given lighting controldevice may ignore the signal. In response to a vacancy signal, the givenlighting control device, when on, may turn its respective lightingload(s) off or may reduce their lighting level(s) to a definedlighting/dimming level(s). How a given lighting control device respondsto occupancy and/or vacancy signals from a given occupancy sensor may bestored at the sensor and conveyed to the lighting control device as partof the signals, may be stored at the lighting control device itself,and/or may be stored at the system controller 250 a, for example, whichmay receive the occupancy and vacancy signals and may subsequentlycontrol the lighting control device. One will recognize that a givenlighting control device may be responsive to signals from more than oneoccupancy sensor. Similarly, multiple lighting control devices may beresponsive to signals from the same occupancy sensor, and may each beconfigured to react differently to the signals. One will also recognizethat load control system 210 a may be configured such that other controldevices (e.g., fan devices, shade devices, thermostat devices, and audiodevices, etc.) may be responsive to occupancy and/or vacancy signalsfrom an occupancy sensor(s). In general, an occupancy sensor may be astandalone device, that is, a device that is separate from the controldevices (such as lighting control devices) that may be responsive to thesignals generated by the sensor. As another example, an occupancy sensormay be integrated with another control device, such as a lightingcontrol device. The control device in which the sensor is integrated maybe responsive to signals generated by the sensor and/or control devicesseparate from the control device in which the sensor is integrated maybe responsive to signals generated by the sensor. One will recognizeother examples are possible. One will recognize that load control system210 a may include other types of control devices.

The information provided by the system controller 250 a may also includefor each control device a location indicator that may indicate alocation of the device within the user environment 202 a and/or thelocation of the electrical loads the device controls. This indicator maybe in the form of a location name (e.g., a text string) and/or anindicator that may be translated into a location name (e.g., a textstring), although other mechanism may be used. For example, assuming theuser environment is a home, possible locations may include standardlocations like “kitchen,” “living room,” “family room,” “dining room,”“master bedroom,” “bedroom,” “master bathroom,” “bathroom,” “basement,”“front porch,” etc. Locations may also include sub-locations in a roomlike “basement—sitting area,” “basement—game area,” basement—work area,”basement—storage area,” etc. Locations may also include userdefined/customized locations like: “Mary's bedroom,” “John's bedroom,”etc. The location of a control device may be programmed into loadcontrol system 210 a (and stored in database 254, for example) by a userwhen installing the system within the user environment 202 a. One willrecognize these are examples.

For lighting control devices, the information provided by the systemcontroller 250 a may also include a type indicator that may indicate atype of a lighting load(s) (also referred to herein as a light(s))controlled by the control device. A type of a lighting load may include,for example, the function/purpose of the lighting load within itsdefined location and/or indicate/suggest a specific location of thelighting load within its defined location (e.g., ceiling light vs floorlamp). A type indicator may be in the form of a name/function (e.g., atext string) and/or an indicator that may be translated into aname/function (e.g., a text string), although other mechanism may beused. As an example, assuming the user environment 202 a is a home,standard types may include ceiling or overhead light, chandelier,pendant(s), table lamp(s), floor lamp(s), sconce(s), sink light(s)(e.g., for a kitchen or bathroom), island light(s) (e.g., for akitchen), closet light(s), etc. Types may also include userdefined/customized types. The type of lighting load may be programmedinto load control system 210 a (and stored in database 254, for example)by a user when installing the system within the user environment 202 a.One will recognize these are examples. Types may also apply to othercontrol devices such as fans, shades, and keypads. Again, the typeindicator may provide an indication of a specific function and orlocation within the device's defined location. Other example types mayinclude “left shade,” “right shade,” “center shade,” “wall keypad,”“tabletop keypad,” etc.

The information provided by the system controller 250 a may also includean indication of an icon to be used with applications (such as thecontrol application) to graphically represent the control device on agraphical interface. The type of icon to associate with a device may beprogrammed into load control system 210 a (and stored in database 254,for example) by a user or automatically when installing the systemwithin the user environment 202 a.

The information provided by the system controller 250 a may also includea current status/state and/or configuration of one or more of thecontrol devices. For example, for a lighting control device the statusinformation may include whether the respective lighting load(s) are inan on or off state, and if in the on state whether it is a dimmed stateand possibly further the dimming level. For a shade device, the statusinformation may include whether the respective shade(s) are open/up,closed/down, partially open/up, and if partially open/up its actuallevel. For a thermostat device and its respective HVAC system, thestatus information may include the setpoint/target temperature of thesystem, the present room temperature as measured by the thermostatdevice, the current mode setting (e.g., heat, cool, auto, off), thecurrent fan setting (e.g., on, auto), and schedule information (e.g., onvs off, assuming the thermostat device is programable to haveschedules). For a ceiling fan device, the status information may includewhether the respective fan(s) are in an on or off state, and if in theon state possibly the fan speed. For an audio control device (e.g., aspeaker system), the status information may include whether the deviceis on/playing music for example, or off and/or muted. For a keypaddevice such as a wall mounted, tabletop, and/or handheld/remote keypad,the status information may include which actuator of the device was lastactuated (i.e., is currently activated) and if the keypad has one ormore actuators corresponding to scenes, the configuration of each scene(e.g., what control devices are part of the scene, the settings of thesedevices for the scene such as light levels or fan speeds, etc.). Thecontrol application may allow the user via the network device to modifythese scenes and to create new scenes. For an occupancy sensor, thestatus information may include, for example, whether the sensor hasdetected an occupancy event/condition and/or is in an occupancy state,has detected a continued occupancy event/condition and/or is in acontinued occupancy state, and/or has detected a vacancy conditionand/or is in a vacancy state. Again, these are examples and otherinformation is possible.

As another example, the system controller 250 a may maintain informationrelated to one or more pre-programmed scenes that may be actuated by auser from an application, such as the control application 1103. A scenemay be, for example, certain settings for one or more lights, shades,etc. The system controller 250 a may maintain respective sceneconfiguration information in database 254. The control application mayobtain from the system controller information related to thesepre-programmed scenes and as further described below, thereafter allowthe user via the network device to a select a given scene, resulting inthe control application instruction the system controller to configurecontrol devices 220 a according to the selected scene (e.g., set onemore light levels, fan speeds, shade levels, etc.). As also describedbelow, the control application may allow a user to modify thepre-programmed scenes maintained by the system controller and to createand store at the system controller new scenes that may subsequently beselected by the user.

As a still further example, the system controller 250 a may maintainvarious timeclock schedules where a schedule may be, for example, acertain setting for one or more control devices (e.g., lights, shades,etc.) that the system controller automatically configures based on aschedule. The system controller 250 a may maintain respective timeclockschedules in database 254 and the status of these schedules, such aswhether a given schedule is active, inactive, or disabled. The controlapplication may obtain from the system control information related tothese timeclock schedules and as further described below, thereafterallow the user via the network device to modify these schedules and tocreate new schedules.

Turning now to FIG. 6A, there is shown a graphical user interface 610that may be initially displayed by the control application to a user vianetwork device 680 upon the application initially starting (such as bythe user selecting and starting the application at the network device).Again, information displayed in user interface 610 may be based oninformation obtained by the control application from the systemcontroller 250 a upon the application being started. User interface 610may include three sections (which may also be referred to herein aspanes or areas or spaces) including a status section (or pane) 620, amenu selection section (also referred to herein as a menu selectionpane, a tab section or a tab pane) 640, and an information section (orpane) 660. As further described below, status section 620 may providethe user with a status/state of control devices 220 a within the loadcontrol system 210 a. Menu selection section 640 may provide the userwith selectable tabs (here, three tabs are shown including a “Devices”tab 642, a “Scenes” tab 644, and a “Schedules” tab 646 although thesection may include fewer or additional tabs, including the three tabsbeing in an order different than that shown). Section 640 may bescrollable left to right for example to display additional tabs, forexample. The control application may change and/or display theinformation in section 660 depending on which tab is selected and thus,section 660 may be depend upon the selected tab. In general, informationsection 660 may provide the user with different status information andcontrols for controlling and/or configuring load control system 210 a.In the example of FIG. 6A, the Devices tab 642 is active (as shown bythe under-bar 643, although other means may be used such as reversehighlighting, etc. to indicate which tab is currently active). Here,section 660 shows information corresponding to the Devices tab 642. Uponthe control application starting, it may default user interface 610 tothe Devices tab 642 being active, although one of the other tabs mayalso be the default-active tab.

Beginning with section 620, as indicated this section may display thestatus/state of one or more control devices 220 a within the loadcontrol system 210 a. In this example, the control application displaysthree icons each indicating different status information. Icon 622 maybe referred to herein as a lighting devices icon that indicates to theuser the number of lighting control devices with respective lightingloads within the load control system that are currently on. Icon 624 maybe referred to herein as a shades devices icon that indicates to theuser the number of shade devices with respective shades within the loadcontrol system that are currently open/up (where open/up may be anyshade state other than fully closed/down). Icon 626 may be referred toherein as a thermostat devices icon that indicates to the user a currenttemperature in the user environment 202 a. One will recognize that fewerand/or additional icons conveying additional and/or other information toa user may be displayed by the control application in section 620. Forexample, FIG. 6B shows another example graphical user interface 601 thatincludes an icon 628 that may be referred to herein as an audio devicesicon that may indicate to the user a status of audio devices within theload control system, such as whether any audio devices are currentlyon/playing music and/or the number of devices that are currentlyon/playing music. The control application may be configured such thatsection 620 is “scrollable” by the user (such as left to right orup/down) in order to display additional icons. As another example,section 620 may be configured such that there are multiple rows of iconsdisplayed at one time to a user. As another example, section 620 mayinclude what is referred to herein as a fans icon 776 as shown in FIG.6L that may indicate to the user a status of fan devices within the loadcontrol system, such as the number of fans that are currently on.Section 620 may also be configurable by the user of the application suchthat only certain icons and corresponding status information are shownto the user, while others are not. According to another example, ifthere is no status to report for a given load control device (such asall lighting devices are off), the control application may not displaythe corresponding icon at all. Other examples are possible. Referencewill now be made in further detail to representative icons that may bedisplayed by the control application in section 620

Beginning with icon 622, as indicated it may be a lighting devices iconthat indicates to the user the number of lighting control devices withrespective lighting loads within the load control system 210 a that arecurrently on. The control application may determine this number based oninformation obtained from the system controller 250 a. A given lightingcontrol device may control more than one lighting load and may controlthese loads in unison (or may individually control these loads todifferent states). According to one example, the control application mayview a given lighting control device and its respective lighting loadsas one device. In this example, as long as one lighting load controlledby the lighting control device is in an on state, the controlapplication may count this as one (1) with respect to the numberassociated with icon 622, regardless of the number of controlled loadsthat are actually controlled by the device (and that may actually beon). Nonetheless, one will recognize that the number associated withicon 622 may represent the actual number of lighting loads controlled byeach lighting control device. Here, the control application may vieweach lighting load controlled by a given lighting control deviceindividually. In this example, the number associated with icon 622 maybe representative of each lighting load. Hence, if two lighting loadscontrolled by a lighting control device are in an on state, the controlapplication may count this as two (2) with respect to icon 622. Fordescription purposes, the control application is described herein fromthe perspective of a lighting control device, where the lighting controldevice and its respective lighting loads are treated as a single unit.In this example of FIG. 6A, the control application has determined basedon information received from the system controller 250 a that eightlighting control devices have loads currently on (where on may include alighting load in a dimmed state and/or a fully on state). The controlapplication may indicate this determination to the user through thedisplayed number “8” associated with the icon 622 as shown in FIG. 6A(although one will recognize that other variations are possible such asdisplaying the word “eight”, or a symbol that represents 8, such as 8dots, etc.). As one example, the control application may actuallyperform the count to determine the number 8 based on informationreceived from the system controller (e.g., search the list of lightingcontrol devices and determine how many are in an on state) or the systemcontroller may perform the count and report the resulting value to thecontrol application. Other variations are possible. In addition todisplaying the number of lighting control devices determined to becurrently on (i.e., that have at least one of its respective lightingloads on), the control application may actively update the number(increment/decrement) that is displayed by icon 622 based on, forexample, the system controller 250 a actively monitoring the on/offstate of lighting control devices in the user environment (e.g., as aresult of a user in the environment turning lights on and off) andasynchronously reporting (such as in “real-time” or as the state changeevent occurs) this information to the control application. As anotheralternative, the control application, subsequent to being started, mayperiodically request from system controller 250 a the status of thelighting control devices and/or lighting loads and update the numberdisplayed by icon 622 based on the response from the system controller250 a. In this fashion, icon 622 allows a user to quickly and easilydetermine from network device 680 whether any lighting loads are on inthe user environment. If no lighting loads are determined to becurrently on, the control application may display the value “0” withicon 622, may display no value with the icon, may not display the iconat all (thereby indicating no lighting control devices are on, etc.).Other variations are possible. For example, rather than displaying anumber with icon 622, the control application may display the icon whenany lighting load is on and not display the icon when all lighting loadsare off. As a still further example, icon 622 may indicate the number oflighting control devices having respective lighting loads in the offstate.

Icon 622 may also be selectable by the user. Upon detecting/determiningthat the user has selected icon 622, the control application may displayto the user via network device 680 the graphical user interface 702 asshown in FIG. 6C. Interface 702 may continue to display to the icon 622and the number of lighting control devices having at least one lightingload determined to be currently on. Interface 702 may also include a“Turn All Lights Off” icon 704 (although other text and/or icons may beused), which may be selectable by the user. Interface 702 may alsoinclude a respective icon 706 for each lighting control device havinglighting loads that are currently on (Again, according to this example,the control application may be configured to treat a lighting controldevice and its respective lighting load(s) as one unit, collectivelyrepresenting the unit as one icon. As an alternative, each lighting loadcontrolled by a lighting control device may be represented by an icon ininterface 702, or some combination thereof). Each of these icons mayalso be selectable by the user. In this example, eight icons 706 areshown in connection with the value “8” as shown with icon 622. Thecontrol application may use the location indicator associated with eachlighting control device to display with each icon an indication of therespective device's/lighting load's location in the user environment (inthis example, textual information such as, “Kitchen,” “Living Room,”“Front Porch,” and “Master Bedroom” are used, although other mechanismsare possible such as segregating icons by location, similar to section660 of FIG. 6A but only displaying icons for devices currently on). Thecontrol application may also use the type indicator associated with eachlighting control device to display in connection with each icon afurther indication of the device's/lighting load's location and/orfunction (in this example, textual information such as, “CeilingLights,” “Pendants,” “Sink Light,” “Sconces,” and “Table Lamps” areused, although other mechanisms are possible). As further shown in FIG.6C, different icons may be used for various lighting controldevices/lighting loads (here, example icons representative of a pendant,table lamp, sconce, and light bulb are used and other icons arepossible). As indicated, the system controller may provide an indicationof the type of icon the control application should use. As anotherexample, the control application may use the location indicator and/ortype indicator associated with each lighting control device, forexample, to determine which icon to use. In general, the controlapplication's use of textual information and customized icons allows theuser to more easily determine the actual lighting control device/lightsin the user environment the icon refers to.

According to a further aspect of interface 702, in a similar fashion tothe control application actively updating the number displayed by icon622 based on, for example, the system controller 250 a activelymonitoring the state of lighting control devices in the userenvironment, the control application may actively update the icons 706displayed to the user as lighting control devices in the userenvironment change state from on to off and off to on (i.e., as lightingloads controlled by the device change state). In other words, as alighting control device turns its respective lighting load(s) on (e.g.,at least one of the loads), the control application may receive anindication of this change from the system controller 250 a (for example,automatically or in response to a query by the control application) anddisplay to the user an additional icon 706 in interface 702 that isassociated with the lighting control device (in addition to incrementingthe number associated with icon 622). Similarly, as a lighting controldevice turns all its respective lighting load(s) off, the controlapplication may receive an indication of this change from the systemcontroller 250 a and remove from interface 702 the icon 706 associatedwith the lighting control device (in addition to decrementing the numberassociated with icon 622). As another example, rather than remove theicon from interface 702, the control application may change theappearance of the icon (e.g., change its color or contrast as comparedto other icons) to signify off. If interface 702 is subsequently closedand then returned to by the user, the control application may now notdisplay the icon. Other variations are possible.

Turning now to icon 704, as indicated, this icon may be selectable bythe user and may allow the user to turn off all lighting control devicesand thus lighting loads that are currently on in the load control system210 a. Upon detecting/determining that the user selected the icon, thecontrol application may communicate one or more messages to the systemcontroller 250 a instructing the system controller to turn all lightingcontrol devices/lights off. Once completed, the system controller 250 amay provide a response to the control application (automatically or inresponse to a query, for example) indicating that the lighting controldevices are now off. In response, the control application may change thenumber associated with icon 622 to “0” for example (or show no value forexample), and remove all icons 704 from interface 702 or change theappearance of the icons, for example. The control application may alsodeactivate icon 704 since all lighting control devices/lights are off(where deactivating may include making the icon non-selectable by a userand/or changing the appearance of icon 704 such as by changing its coloror contrast as compared to other icons, removing the icon from interface702, etc.). Once a lighting control device returns to the on state (suchas by a user in the user environment 202 a turning a light on), inaddition to incrementing the number associated with icon 622 to “1” forexample, and displaying an icon 704 in interface 702 representing thelighting control device, the control application may alsoactivate/re-activate icon 704 (where activating the icon may includemaking the icon selectable by a user and/or changing the appearance oficon 704 such as by changing its color or contrast as compared to othericons, displaying the icon in interface 702, etc.). One will recognizethat other examples are possible such as interface 702also/alternatively including a “Turn All Lights On” icon, which uponselection, may cause the control application to communicate one or moremessages to the system controller to turn all lights in the userenvironment to an on state (or a pre-programmed set of lights to an onstate). Again, such an action by a user may cause the controlapplication to increment the number associated with icon 622 and todisplay respective icons 706 accordingly. As an alternative and/or inaddition to selecting icon 704, icons 706 may also be selectable by theuser and allow the user to individually control the lighting controldevices and thus lights/lighting loads associated with the icons (Onewill recognize that as an alternative, if the control application isconfigured to show icons 706 in a fashion that indicates the respectivelighting control device is off, the icon may continue to be selectableby the user to also control the device.) Upon detecting/determining thatthe user selected a given one of the icons 706, the control applicationmay display to the user an interface to control the respective device.

For example, assuming the control application detects/determines thatthe user selects the icon 706 labeled “Kitchen Ceiling Lights,” thecontrol application may display the control interface 708 shown in FIG.6D (in this example, the lights are controlled as one to a commonstate). Control interface 708 may be shown alone or superimposed overinterface 702, for example. One will recognize that control interface708 is an example and other controls are possible. The controlapplication may determine based on information provided by the systemcontroller (e.g., from the type indicator) whether the “Kitchen CeilingLights” are configured as dimmable lights or simply on/off lights etc.and based on that determination may display an appropriate controlinterface. In this example, the “Kitchen Ceiling Lights” may beconfigured as dimmable lights and as such, the control application maydisplay control interface 708 with a movable/slide-able actuator 710(e.g., a vertically movable actuator) that may be actuated/moved by theuser. The control application may initially display the actuator 710, asin this example, to provide an indication to the user of a currentdimming state of the lights (e.g., the actuator is approximately mid-wayalong its possible path). Based on detecting movement of actuator 710 bythe user (such as raising or lowering the intensity of the lights,turning the lights off, etc.), the control application may communicateone or more messages to the system controller 250 a to instruct thecontroller to reconfigure the lighting control device/lights based onthe user's instructions. If the user turns the lights off such as bymoving the actuator 710 to its lowest most position at 709, this updatemay be reflected in icon 622 (e.g., decrementing the number) andinterface 702 as similarly discussed above by removing or altering theappearance of the icon 706 corresponding to the “Kitchen CeilingLights.” As shown in FIG. 6D, control interface 708 may also include aselectable “Edit” icon 712 that when selected, may cause the controlapplication to display a user interface that may allow a user toreconfigure the respective lighting control device/lights (here, the“Kitchen Ceiling Lights”). For example, referring to FIG. 6E, there isshown an example configuration interface 790 the control application maydisplay to a user upon detecting selection of the “edit” icon 712.Interface 790 may include a field 791 and/or an actuator/icon 791′configured to enable a user to change the type indicator (here “CeilingLights”) associated with the lighting control device, (e.g., through adrop-down menu of defined types obtained via actuation of actuator 791′,a free text field 791, etc.) Interface may also include an actuator/icon792 configured to enable a user to change the location indicator (here,“Kitchen”) associated with the lighting control device (e.g., through adrop-down menu of defined locations obtained via actuation of actuator792). Interface 790 may include an actuator/icon 793 configured toenable a user to change the icon associated with the lighting controldevice/lights (e.g., through a drop-down menu of defined icons obtainedvia actuation of actuator 793). The interface may include anactuator/icon 794 configured to enable a user to adjust or configure thetrim level of the lighting control device/lights, such as a low-end trimlevel (e.g., a minimum light level the light(s) may be controlled toand/or a high-end trim level (e.g., a maximum light level the light(s)may be controlled to) (e.g., through a drop-down menu of defined trimlevels obtained via actuation of actuator 794). Interface 790 mayinclude an actuator/icon 795 configured to enable a user to adjust orconfigure whether the lighting control device controls the dimming levelof its respective light(s) via either forward phase dimming or reversephase dimming (e.g., through a drop-down menu obtained via actuation ofactuator 795). Again, the control application may display editablefeatures of a lighting control device (such as trim and phase) based ona determination that the lighting control device controls dimmablelight(s). The interface may also include a “Delete Device” icon 796.Actuation of this icon 796 may cause the control application to instructthe system controller to remove the lighting control device from theload control system. Assuming the user makes changes to the lightingcontrol device via interface 790, once done the user may select “Save”or “Cancel” (although other mechanisms may be used) as shown in theinterface to return to control interface 708 for example and to save ornot save the changes/configurations. Any saved changes made by the userregarding the editing of the lighting control device may be communicatedby the control application to the system controller, which may thenreconfigure the lighting control device accordingly. One will recognizethat control interface 708 and configuration interface 790 are examplesand other controls are possible. A user may exit control interface 708by touching an area of the display screen of network device 680 outsideof the interface 708. Other examples are possible.

As another example of a control interface to control a lighting controldevice, assume that interface 702 includes an icon 706 for a table lampin the master bedroom, that the icon is labeled “Master Bedroom MasterReading,” and that the control application detects/determines that theuser selects this icon 706 from interface 702. In response thereto, thecontrol application may display the example control interface 2100 shownin FIG. 10A. One will again recognize that control interface 2100 is anexample and other control interfaces are possible. One will furtherrecognize that control interface 2100 may be displayed to a user inresponse to other actions by the user via other interfaces and/or inresponse to other determinations made by the control application and/orsystem controller. The control application may determine based oninformation provided by the system controller (e.g., from the typeindicator) whether the “Master Bedroom Master Reading” table lamp isconfigured as a dimmable lighting load or simply an on/off lighting loadetc. and based on that determination may display an appropriate controlinterface. In this example, the “Master Bedroom Master Reading” tablelamp may be configured as dimmable lighting load and as such, thecontrol application may display control interface 2100 to providedimming control. According to this example, control interface 2100 mayinclude an actuator 2102 (which may be referred to herein as a dimmingactuator for example) that is movable/slide-able (e.g., verticallymovable) along control line 2108 c, an increase actuator 2104 a and adecrease actuator 2104 b, and an on/off actuator 2106.

Beginning with actuator 2106, as shown in this example it may bedisplayed as an icon that resembles the icon shown in interface 702,although one will recognize that other icons and/or controls may beused. Actuator 2106 may be selectable by a user to turn the lightingcontrol device (and thus the respective light(s)/lighting load(s)) onand off. According to one example, the control application may displaythe appearance of actuator 2106 differently based on the on/off state ofthe lighting load (e.g., change the icon's color or contrast). Forexample, FIGS. 10A and 10C (as discussed below) show an example thatuses reverse contrast to show the on/off states, with FIG. 10A showingactuator 2106 in a state that represents that the lighting load is on,and with FIG. 10C showing the actuator 2106 in a state that representsthat the lighting load is off. One will recognize that other examplesare possible.

Turning to actuator 2102, it may be an actuator that ismovable/slide-able (e.g., a vertically movable, although one willrecognize that actuator 2102 may alternatively be horizontally moveable,for example) along control line 2108 c and that allows a user toincrease the intensity/intensity level or brightness of the lightingload (e.g., by moving the actuator vertically upward towards position2108 a) or decrease the intensity of the lighting load (e.g., by movingthe actuator vertically downward towards position 2108 b). Actuator 2102may allow a user to control the intensity of the lighting load from amaximum intensity such as 100% (position 2108 a) to a minimum intensity,which may be 0% (position 2108 b) and which thereby may turn thelighting load off. In other words, moving actuator 2102 to position 2108b may turn the lighting load off. The control application may displaythe position of actuator 2102 along control line 2108 c to represent thecurrent relative intensity of the lighting load. The control applicationmay also display with actuator 2106 an indicator 2109 that numericallyrepresents the current intensity of the lighting load, here shown as anumerical percentage value 70% although other example numericalrepresentations may be used. As one example, indicator 2109 may vary invalue between 0% to 100%, with 0% representing off. The controlapplication may also dynamically vary the value of indicator 2109 as theuser moves actuator 2102 vertically upward and downward. As also shownin FIG. 10A, the portion of control line 2108 c that lies below theactuator 2102 may be shown in a different intensity or line thickness,for example (here a greater intensity/line thickness) than the portionof the control line 2108 c that lies above the actuator 2102

Similar to actuator 2102, increase actuator 2104 a and decrease actuator2104 b may also enable a user to increase and decrease, respectively,the intensity of the lighting load. As one example, each of actuators2104 a and 2104 b may be selectable in a single action (e.g., by a clickand release of a mouse button, or a touch and release of the displayscreen of network device 680). Here, each individual actuation ofincrease actuator 2104 a may increase the intensity of the lighting loadby a defined amount (e.g., 1%) and similarly, each individual actuationof decrease actuator 2104 b may decrease the intensity of the lightingload by a defined amount (e.g., 1%). The defined amount may be userdefinable. As another example, each of actuators 2104 a and 2104 b maybe selectable for a prolonged duration (e.g., by a press and prolongedrelease of a mouse button, or a prolonged touch of the display screen ofnetwork device 680). Here, the actuation may cause the intensity toincrease/decrease until the mouse button is released or the touch of thescreen is removed, for example. According to one example, as a userselects the increase actuator 2104 a or the decrease actuator 2104 b,the control application may also automatically move actuator 2102 in theup or down direction, respectively, and update the value of indicator2109 accordingly.

In general, upon the control application initially detecting/determiningthat the user selects the icon 706 labeled “Master Bedroom MasterReading” from interface 702 for example, it may initially display theactuator 2102 and the actuator 2106 of control interface 2100 to providean indication to the user of a current on/off state and dimming state ofthe lighting load. For example, assuming the lighting load is on and isin a dimmed state of 70% intensity, the control application may displaythe control interface 2100 as shown in FIG. 10A, with actuator 2106shown to indicate the lighting load is on and with actuator 2102 at arelative position along control line 2108 c to represent 70% intensityand with the value of indicator 2109 showing the value 70% for example.Similarly, assuming the lighting load is off, the control applicationmay display the control interface 2100 as shown in FIG. 10C, withactuator 2106 shown to indicate the lighting load is off and withactuator 2102 at position 2108 b to represent 0% intensity/the lightingload is off, and with the value of indicator 2109 showing the value 0%for example. With reference to indicator 2109, initially the value maybe displayed in one intensity and/or color, such as shown in FIGS. 10Aand 10C. Once the user (and/or as the user) selects any of actuators2102, 2104 a, 2104 b, and/or 2106 for example, the control applicationmay increase the intensity (or change the color) of indicator 2109, asshown in FIG. 10B, with the increased intensity. At a defined time afterthe user stops altering the dimming state and/or the on/off state of thelighting load (or when the user stops actuating any of the actuators),the control application may return indictor 2109 to a reduced intensityas shown in FIG. 10A (and/or revert the color back to the initialcolor). One will recognize that other examples are possible.

In general, if the lighting load is in an on state as shown in FIG. 10Aand the user actuates actuator 2106 to turn the lighting load off, thecontrol application may display control interface 2100 as shown in FIG.10C, with actuator 2106 displayed to show the lighting load is off andwith actuator 2102 automatically moved to position 2108 b and indicator2109 set to 0% to show an off state. Similarly, if the lighting load isin an off state as shown in FIG. 10C and the user actuates actuator 2106to turn the lighting load on, the control application may displaycontrol interface 2100 as shown in FIG. 10A, with actuator 2106displayed to show the lighting load is on and with actuator 2102automatically moved to a relative position along control line 2108 c toshow the current intensity of the lighting load and with indicator 2109displaying the intensity value (here, the system controller and/orcontrol application, for example, may maintain a last set dimming leveland/or a preferred dimming level and may automatically set the dimminglevel of the lighting load to this value upon the lighting load beingturned on). Similarly, if the lighting load is in an on state as shownin FIG. 10A and the user actuates actuator 2106 or 2108 b to turn thelighting load off (i.e., dim to 0%), the control application may displaycontrol interface 2100 as shown in FIG. 10C, with actuator 2106displayed to show the lighting load is off and with actuator 2102 shownin position 2108 b and the value of indicator 2109 set to 0% to show anoff state. Similarly, if the lighting load is in the off state as shownin FIG. 10C and the user actuates actuator 2106 or 2108 a to turn thelighting load on (i.e., increase the intensity), the control applicationmay display control interface 2100 as shown in FIG. 10A, with actuator2106 displayed to show the lighting load is on and with actuator 2102moved to an intensity position along control line 2108 c as selected bythe user and the value of indicator 2109 showing the current intensityvalue. One will recognize that other examples are possible.

Overall, based on detecting the selection/movement of actuator 2102and/or actuators 2104 a and 2104 b by the user (such as raising orlowering the intensity of the lighting load, turning the lighting loadoff, etc.), and/or detecting the selection of actuator 2106 by the user(such as turning the lighting load on and off), the control applicationmay communicate one or more messages to the system controller 250 a, forexample, to instruct the controller to reconfigure the lighting controldevice/lighting load(s) based on the user's instructions. Again, if theuser turns the lighting load off or on, this update may be reflected inicon 622 (e.g., decrementing/incrementing the number), etc. A user mayexit control interface 2100 by selecting icon 2101, for example. Otherexamples are possible.

According to another example, a lighting control device may control alighting load (or a plurality of lighting loads), where the lightingload may include a plurality of multi-colored LEDs (light emittingdiodes), although one will recognize that other types of lighting loadsconfigured to emit colors of various color temperatures may be used. Inother words, the lighting load may include within a single package, forexample, a number of differently colored emission LEDs and may beconfigured such that the chromaticity output of the LEDs is mixed toproduce light having varying chromaticity coordinates (i.e., colorpoints) within a color gamut formed by the various LEDs that make up thelighting load. As one example, a lighting load may include one or morered LEDs, one or more green LEDs, one or more blue LEDs, and one or morewhite, or substantially white LEDs (such as yellow and/or mint greenLED(s)), which may be collectively referred to herein as a RGBW lightingload. Although an RGBW lighting load is described herein with acombination of four LEDs of certain colors, this is for example purposesand other combinations of LEDs (e.g., more or less LEDs and/or differentcolor LEDs) may be used. Similarly, although an RGBW lighting load isdescribed herein as having one or more white LEDs, other colored LEDsmay be used instead, such as yellow or mint green LED(s). Again, RGBWLED lighting loads will be used herein for description purposes only,and other types of lighting loads configured to produce light of varyingcolor temperatures may be used.

A lighting control device and such a respective lighting load may beconfigured to produce white or near-white light of varyingbrightness/intensities within a range of correlated color temperatures(CCTs) ranging from “warm white” (e.g., roughly 2600 K-3700 K), to“neutral white” (e.g., 3700 K-5000 K) to “cool white” (e.g., 5000 K-8300K), for example (e.g., produce light of varying chromaticity coordinatesthat lie along the black body locus or curve). As a further example,such a lighting control device and its respective lighting load may befurther configured to produce any color of varyingbrightness/intensities within the color gamut formed by the various LEDsthat make up the lighting load.

According to a still further example described herein, such a lightingcontrol device and its respective lighting load may be configured to oneof two states or modes, including a non-vibrancy state/mode and avibrancy state/mode (e.g., where the system may automatically select fora user a certain vibrancy level). The chromaticity coordinates of themixed color output of the lighting load may be the same (orapproximately the same) between the two modes (e.g., when in anon-vibrancy mode versus a vibrancy mode). However, the intensities ofthe various LEDs (and thus the intensities of the wavelengths that areproduced by the LEDs) may be varied between the two modes such that inthe vibrancy mode, the intensity of the white LED(s) for example, may bereduced (such as to 0%, for example) as compared with the non-vibrancymode, with the intensities of the remaining red, green, and/or blue LEDsadjusted to maintain the same color output (or approximately the same)between the two modes. Similarly, non-vibrancy mode may increase theintensity of the white LED(s) (with the intensities of the remainingred, green, and/or blue LEDs adjusted to maintain the same color output(or approximately the same color output) as when in the vibrancy mode).

As such, as described herein, vibrancy mode may, for example, increasethe intensity of one or more wavelengths produced by the red, green,and/or blue LEDs thereby causing certain objects within a space to lookmore “vibrant”. In other words, vibrancy mode, as described herein, maytune the individual colors that make up the light at a given color. Whenvibrancy is adjusted, the color of the light (e.g., the chromaticitycoordinates or the CCT value) may remain unchanged or substantiallyunchanged. Adjusting vibrancy may, however, adjust the contribution ofthe individual LEDs making up the given light output at a given color.Hence, the light reflected off of objects in the space may be morevibrant as vibrancy is increased (vibrancy mode), and similarly lessvibrant as vibrancy is decreased (non-vibrancy mode). In addition,adjusting vibrancy may adjust spectral power distribution (SPD) of thelight. For example, as vibrancy increases, an SPD curve of the emittedlight (e.g., relative intensity vs wavelength) may become sharper and/ormay result in individual colors on the objects appearing more vibrantwhen the light reflects off of them. Hence, according to one example asdescribed herein, the difference between the vibrancy and non-vibrancymodes may be the intensity setting of the white LED(s)/the amount thewhite LED(s) contribute to the mixed color output of the lighting load,with the white LED(s) contributing less in vibrancy mode as compared tonon-vibrancy mode (as another example, if mint green LEDs are used, forexample, instead of white LEDs, the intensity setting of the mint greenLED(s)/the amount the mint green LED(s) contribute to the mixed coloroutput of the lighting load may be less in vibrancy mode as compared tonon-vibrancy mode). One will recognize that other examples are possible.One example of a lighting control device and respective lighting load asdescribed above is a luminaire or lamp as provided by Lutron Ketra.Another example of such a lighting control device and respectivelighting load is described as illumination device 38 of U.S. PatentApplication Publication Number 2018/0077770, the contents of which arehereby incorporated by reference in their entirety. One will recognizethat other examples lighting control device and respective lightingloads are possible.

As referred to herein, vibrancy mode may be referred to as a highvibrancy mode or a vibrancy “on” setting, and non-vibrancy mode may bereferred to as a low vibrancy mode or a vibrancy “off” setting (whichmay be a “normal” setting).

Assuming now that the “Master Bedroom Master Reading” table lamp icon ofinterface 702, for example, corresponds to a lighting control devicethat controls a RGBW lighting load as described above, upon the controlapplication detecting/determining that the user selects the “MasterBedroom Master Reading” table lamp icon from interface 702, the controlapplication may display the example control interface 2110 shown in FIG.11A. One will again recognize that control interface 2110 is an exampleand other control interfaces are possible. One will further recognizethat control interface 2110 may be displayed to a user in response toother actions by the user via other interfaces and/or in response toother determinations made by the control application and/or systemcontroller. The control application may determine based on informationprovided by the system controller (e.g., from the type indicator, etc.)that the “Master Bedroom Master Reading” table lamp is configured as adimmable RGBW LED lighting load and based on that determination maydisplay control interface 2110. As one for example, as noted above thesystem controller may provide information on each lighting controldevice to the control application. This information may include for anRGBW control device/lighting load its current status/state and/orconfiguration. For example, the information may include for an RGBWlighting control device/lighting load(s) whether the lighting load(s)are in an on or off state, and if in the on state whether it is a dimmedstate and possibly further the dimming level, what color point and/orCCT value the load is set or configured to, whether the control deviceis in vibrancy mode, etc. Control interface 2110 may be similar tocontrol interface 2100 and may include an actuator 2112 (which may bereferred to herein as a dimming actuator for example) (and control line2118 c with ends 2118 a and 2118 b) and my further include actuators2114 a and 2114 b that operate similar to actuator 2102 and actuators2104 a and 2104 b, respectively, and enable a user to control theintensity/brightness/dimming state of the lighting load as describedabove (i.e., change the intensity/brightness of the color being producedby the lighting load).

Control interface 2110 may also include an actuator 2116 that similar toactuator 2106, may be selectable by a user to turn the lighting controldevice (and thus the respective lighting load(s)) on and off. Again, thecontrol application may display the appearance of actuator 2116differently based on the on/off state of the lighting load, with FIG.11A showing actuator 2116 in a state that represents that the lightingload is on, and with FIG. 11C showing the actuator 2116 in a state thatrepresents that the lighting load is off. One will recognize that otherexamples are possible. According to a further aspect of this example,when the lighting load is in an on state as shown in FIG. 11A, theactuator 2116 may further include an indicator 2117 (which may bereferred to herein as a color indicator for example). In this example,indicator 2117 is shown as a circle that surrounds the actuator 2116.Nonetheless, one will recognize that other indicators may be usedincluding different geometric shaped indicators such as a square ortriangle that surrounds actuator 2116, or an indicator that is next toactuator 2116 rather than surrounding it, or an indicator that is at adifferent location within control interface 2110. The controlapplication may display indicator 2117 in any of a plurality ofdifferent colors and in particular, may display the color of indicator2117 to match (or to substantially match) or represent the colorcurrently being produced by the lighting load. In this fashion, the useris provided with an indication as to the current color setting of thelighting load. As shown in FIG. 11C, the control application may notdisplay indicator 2117 when the lighting load is off. Again, as thelighting load is moved between an on and off state such as through theactuation of actuator 2116 or moving actuator 2112 (either directly orthrough actuators 2114 a and 2114 b) to and from position 2118 b, thecontrol application may change the appearance of actuator 2116 (betweenan on/off state) and display or not display indicator 2117. One willrecognize that as an alternative to and/or in addition to displaying the“actual” color being produced by the lighting load through indictor2117, the control application may also display in control interface 2110for example, chromaticity coordinates (such as x and y coordinates) orthe CCT value (when applicable) of the color being produced by thelighting load. One will recognize that other examples are possible.

With reference to indicator 2119 (which is similar to indicator 2109)and as discussed above, initially the value of the indicator may bedisplayed in one intensity, such as shown in FIGS. 11A and 11C. Once theuser selects any of actuators 2112, 2114 a, 2114 b, and/or 2116, thecontrol application may increase the intensity of indicator 2119, asshown in FIG. 11B. At a defined time after the user stops altering thedimming state and/on/off state of the lighting load, the controlapplication may return indictor 2119 to a reduced intensity.

As similarly discussed with reference to interface 2100, based ondetecting the selection/movement of actuator 2112 and/or actuators 2114a and 2114 b by the user (such as raising or lowering the intensity ofthe lighting load, turning the lighting load off, etc.), and/ordetecting the selection of actuator 2116 by the user (such as turningthe lighting load on and off), the control application may communicateone or more messages to the system controller 250 a, for example, toinstruct the controller to reconfigure the lighting controldevice/lighting load(s) based on the user's instructions. Again, if theuser turns the lighting load off or on, this update may be reflected inicon 622 (e.g., decrementing/incrementing the number), etc. A user mayexit control interface 2110 by selecting icon 2101, for example. Otherexamples are possible.

According to a further aspect of control interface 2110, the interfacemay include a “Warm/Cool” actuator 2120, a “Vibrancy” actuator 2122, anda “Full Color” actuator 2124 (one will recognize that labels other than“Warm/Cool”, “Vibrancy,” and “Full Color” may be used). Each ofactuators 2120, 2122, and 2124 may be selectable by a user.

Beginning with “Vibrancy” actuator 2122, upon detecting selection ofthis actuator by a user the control application may communicate one ormore messages to the system controller 250 a, for example, to instructthe system controller to configure the lighting control device/lightingload to enter a vibrancy mode (e.g., turn vibrancy to an on setting orto a high mode). As indicated above, vibrancy mode may not change (orsubstantially change) the color point/chromaticity coordinates of thecolor being produced by the lighting load, but may alter thecontribution/intensity of each of the RGBW LEDs in generating thecolored light, which may include reducing the intensity/contribution ofthe white LED(s) for example (e.g., setting the intensity of the whiteLEDs to 0%), thereby making certain objects in a space more vibrant. Onewill recognize this is one example, and vibrancy may be achieved inother manners. The one or more messages communicated by the controlapplication to the system controller may include a command to entervibrancy mode, may include a command with specified intensity settingsfor each of the various RGBW LEDs, etc., although other examples arepossible. In general, the degree to which the intensities of the variousRGBW LEDs is varied when entering vibrancy mode may be a predefinedamount and in addition, may be dependent upon the colorpoint/chromaticity coordinates of the color currently being produced bythe lighting load. For example, the closer the color of the light beingproduced by a lighting load is to the black body curve (i.e., when thelighting load is producing white light), there may be a greater abilityto place the lighting load in vibrancy mode (as compared to when thecolor of the light is further away from the black body curve).

In response to detecting selection of the “Vibrancy” actuator 2122, thecontrol application may display the appearance of actuator 2122differently based on whether the lighting control device is or is not invibrancy mode (e.g., change the actuator's color or contrast). Forexample, FIGS. 11A and 11D show an example that uses reverse contrast toshow the states of the vibrancy mode, with FIG. 11A showing vibrancymode deactivated (low vibrancy mode/off), and with FIG. 11D showing thevibrancy mode activated (high vibrancy/on). One will recognize thatother examples are possible. When vibrancy mode is activated, upondetecting a further selection of actuator 2122 by a user the controlapplication may communicate one or more messages to the systemcontroller 250 a to instruct the controller to configure the lightingcontrol device/lighting load to deactivate vibrancy mode (e.g., setvibrancy to an off-setting or to a low mode), thus maintaining the coloroutput of the lighting load, but increasing the contribution of thewhite LED(s) for example (for example, something other than 0%) ascompared to when vibrancy mode is activated. This state may be referredto herein as a “normal” setting. Again, upon the control applicationinitially detecting/determining that the user selects the icon 706labeled “Master Bedroom Master Reading” from interface 702 for example,it may initially display the actuator 2122 as vibrancy mode beingactivated or not activated, depending on the current state of thelighting control device as reported by the system controller. Inaddition, even when the lighting control device is in an on state and isin vibrancy mode with actuator 2116 and actuator 2122 as shown in FIG.11D, upon the lighting load being turned off, the control applicationmay display actuator 2122 as vibrancy mode being off, as shown in FIG.11C. One will recognize that other examples are possible.

Reference is now made to “Warm/Cool” actuator 2120 and “Full Color”actuator 2124. “Warm/Cool” actuator 2120 may allow a user to control thelighting control device such that the lighting load produces light(e.g., white or near white light) at a user selected color point alongthe black body curve. “Full Color” actuator 2124 may allow a user tocontrol the lighting control device such that the lighting load produceslight at a user selected color point of any of a plurality of colorsthat may lie within the color gamut formed by the various RGBW LEDs, forexample, that make up the lighting load.

Beginning with “Warm/Cool” actuator 2120, upon detecting that a user hasselected the actuator (such as from interface 2110 (or from interface2140 of FIGS. 11J-11N as discussed below), the control application maydisplay control interface 2130 as shown in FIG. 11E, with the“Warm/Cool” actuator 2120 now being shown as activated (here, reversecontrast is used to show “Warm/Cool” actuator 2120 as being activated,although other examples are possible). Control interface 2130 maycontinue to include actuators 2112, 2114 a, and 2114 b (together withindicator 2119) that allow a user to control the intensity of thelighting load and also provide the user with the current dimming stateof the lighting load. Control interface 2130 may also continue toinclude actuator 2116 that enables to the user to turn the lightingcontrol device/lighting load on and off. Control interface 2130 may alsocontinue to include indicator 2117 to provide the user with anindication of the current color being produced/rendered by the lightingload. According to this example, control interface 2130 may also includea pallet 2135 showing a range of colors ranging from cool colors at end2135 a to warm colors at end 2135 b of the pallet. These colors maycorrespond to colors that lie along the black body curve. In particular,pallet 2135 may show colors along a range of correlated colortemperatures (CCTs) ranging from “warm white” (e.g., roughly 2600 K-3700K) at 2135 b, to “neutral white” (e.g., 3700 K-5000 K) to “cool white”(e.g., 5000 K-8300 K) at 2135 a. As one example, the range may be from1400K to 7000K, although other examples are possible.

Superimposed over pallet 2135 may be an actuator 2132 that ismovable/slide-able (e.g., here vertically movable) along control line2135 c and in particular, that is movable/slide-able along pallet 2135between different CCTs along the black body curve. Accordingly, actuator2132 may allow a user to configure the lighting control device such thatthe lighting load produces colored light at a color point along theblack body curve. Assuming the lighting load is producing light at acolor point along the black body curve at a time actuator 2120 isselected by a user, the control application may display actuator 2132 ata relative point along control line 2135 c/pallet 2135 as shown in FIG.11E to indicate the color being produced by the lighting load.Similarly, indicator 2117 may also display the corresponding color.Alternatively, if the lighting load is not configured to produce lightat a color point along the black body curve (or is out of range ofpallet 2135) (or if the lighting load is off, for example) at a timeactuator 2120 is selected by a user, the control application may notdisplay actuator 2132. The control application may continue to displayindicator 2117 to correspond to the color being produced by the lightingload (assuming the lighting load is on). As another example, regardlessof the setting of the lighting load, the control application may notinitially display actuator 2132 upon selection of actuator 2120.

Assuming that upon actuator 2120 being actuated by a user from controlinterface 2110 that the control application initially displays controlinterface 2130 as shown in the FIG. 11E with actuator 2132 displayed,for example, and assuming a user next selects/moves actuator 2132 alongcontrol line 2135 c (such as via a mouse or via touch) to set thelighting load to a new CCT along the black body curve, the controlapplication may display an indicator 2136 together with the actuator asshown in FIG. 11F. As another example, assuming actuator 2132 is notinitially shown when actuator 2120 is selected by a user, selectingpallet 2135 (e.g., via mouse or touch) by the user may cause theactuator 2132 and indicator 2136 to appear at a location along line 2135c relative to where the user touches pallet 2135 and/or at a locationrelative to the CCT the lighting load is currently providing. One willrecognize that other examples are possible. The indicator 2136 maydisplay a numerical value (in this example, 6500 K) that corresponds tothe CCT value the actuator 2132 is currently set to. As the user movesthe actuator 2132 along the control line 2135 c, the control applicationmay dynamically update indicator 2136 to correspond to the setting ofthe actuator. In addition and as shown in FIG. 11F, as the user movesthe actuator 2132 along the control line 2135 c, the control applicationmay dynamically update indicator 2117 to correspond to the color atwhich the actuator 2132 is currently set to. According to a furtherexample and as shown in FIG. 11F, the control application may alsoincrease the size of indicator 2117. In this example, indictor 2117 isshown as a circle where the weight of the line forming the circle isheavier or larger or thicker in FIG. 11F as compared to FIG. 11E forexample. One will recognize that other examples are possible. In thisfashion, the control application may provide an additional mechanism toshow the user the color the lighting load is being set to and alsoindicate to the user that the color is being changed. According to astill further example, at a set time duration after which the user stopsactuating actuator 2132 and/or upon the user no longer selecting theactuator, the control application may remove indicator 2136 from thecontrol interface and return indicator 2117 to a smaller size/lighterweight, as shown in the example of FIG. 11G. One will recognize thatindictor 2136 may include or be a different value, such as chromaticitycoordinates (such as x and y coordinates) of the color being produced bythe lighting load. Similarly, rather than increase the size of indicator2117 as actuator 2132 is moved in order to display a color to the user,other mechanisms may be used to show the color to the user, such as byrendering actuator/icon 2116 in the color as the actuator is activated.

According to a still further example, assuming the lighting load is offwhen a user selects actuator 2120 thereby causing control interface 2130to be displayed by the control application, a user selecting pallet 2135(e.g., via mouse or touch) may cause the lighting load to turn on (suchas to full intensity, to an intensity to which the lighting load waspreviously set to, or to a preferred intensity level of the user, etc.),and with the appearance of actuator 2116 changing to an on state,indicator 2117 being displayed, and with actuator 2112 being displayedat the present intensity level. Similarly, actuator 2132 and/orindicator 2136 may appear at a location along line 2135 c relative towhere the user touches pallet 2135 and/or at a location relative to theCCT the lighting load was previously set to, or to a preferred CCT valueof the user, although other examples are possible, and with the lightingload being controlled to this color (again, with indicator 2117 alsoindicating the color). Thereafter, a user may move actuator 2132 asdescribed above.

As similarly discussed above, based on detecting the selection/movementof actuator 2132, the control application may communicate one or moremessages to the system controller 250 a, for example, to instruct thecontroller to reconfigure the lighting control device/lighting load(s)based on the user's instructions.

As shown in FIG. 11H while the lighting load is set to a color pointalong the black body curve, a user may also actuate from controlinterface 2130 any of actuators 2112, 2114 a, and/or 2114 b to controlthe dimming state/intensity of the lighting load. Again, as this occurs,the control application may increase the intensity of indicator 2119 asshown in FIG. 11H. Similarly, as shown in FIG. 11I, while the lightingload is set to a color point along the black body curve, a user may alsoactuate from control interface 2130 the “Vibrancy” actuator 2122 toconfigure the lighting control device/lighting load to enter vibrancymode. As indicated above, vibrancy mode may not change (or substantiallychange) the color point/chromaticity coordinates/CCT value of the colorbeing produced by the lighting load, but may alter the contribution ofeach of the RGBW LEDs in generating the colored light, which may includereducing the intensity/contribution of the white LED(s) for example,thereby making certain objects in a space more vibrant. In response todetecting selection of the “Vibrancy” actuator 2122, the controlapplication may display the appearance of actuator 2122 to show it isactivated, as shown in FIG. 11I, and communicate one or more messages tothe system controller 250 a, for example, to instruct the systemcontroller to configure the lighting control device/lighting load toenter a vibrancy mode. While the “Vibrancy” actuator 2122 is activatedand a user modifies the color and or intensity of the lighting load viacontrol interface 2130, the color rendered by the lighting load maycontinue to be in the “vibrant” state/vibrancy mode. Similarly, a usermay deactivate vibrancy mode from control interface 2130 thus returningto a normal setting (thus maintaining the color output of the lightingload, but increasing the contribution of the white LED(s) for example).Lastly, assuming a user turns the lighting load off (such as through anyof actuators 2116, 2112, 2114 a, and/or 2114 b) as described hereinwhile control interface 2130 is displayed, the control application mayautomatically display control interface 2110 as shown in FIG. 11C. Onewill recognize that other examples are possible. One will also recognizethat actuator 2124 may be activated from control interface 2130,resulting in the control application displaying control interface 2140,for example, as discussed below.

Turning now to “Full Color” actuator 2124, upon detecting that a userhas selected the actuator (such as from interface 2110 or interface2130), the control application may display control interface 2140 asshown in FIG. 11J, with the “Full Color” actuator 2124 now being shownas activated (here, reverse contrast is used to show Full Color actuator2124 as being activated, although other examples are possible). Controlinterface 2140 may continue to include actuators 2112, 2114 a, and 2114b (together with indicator 2119) that allow a user to control theintensity of the lighting load and that also provide the user with thecurrent dimming state of the lighting load. Control interface 2140 mayalso continue to include actuator 2116 that enables to the user to turnthe lighting control device/lighting load on and off. Control interface2140 may also continue to include indicator 2117 to provide the userwith an indication of the current color being produced/rendered by thelighting load. According to this example, control interface 2140 mayalso include a pallet 2145 showing a plurality of colors that lie withinthe color gamut formed by the various RGBW LEDs, for example, that makeup the lighting load.

As shown in FIG. 11K, superimposed over pallet 2145 may be an actuator2142 that is movable/slide-able by the user to any of a plurality oflocations/colors within pallet 2145. The control application may displaytogether with actuator 2142 two perpendicular control lines 2144 a and2144 b that intersect at the center 2144 c of the actuator 2142. Thecontrol application may move control lines 2144 a and 2144 b and theintersection point with the actuator 2142 as it is moved by a userwithin pallet 2145. These control lines may also assist the use inmoving actuator 2142 either horizontally or vertically. Accordingly,actuator 2132 may allow a user to configure the lighting control devicesuch that the lighting load produces colored light at a color point thatlies within the color gamut formed by the various RGBW LEDs, forexample, that make up the lighting load. Upon actuator 2124 beingactuated by a user such as from control interface 2110 or 2130 forexample, the control application may initially display control interface2140 without actuator 2142 and without control lines 2144 a and 2144 b,as shown in FIG. 11J (such as if the lighting load is off, or even whenthe lighting load is presently on). Indicator 2117 may continue,however, to be displayed to the user (assuming the lighting load is on),showing the color the lighting load is currently providing. As anotherexample, upon actuator 2124 being actuated by a user the controlapplication may display actuator 2142 and control lines 2144 a and 2144b at a relative point within pallet 2145 to indicate the color beingproduced by the lighting load. Again, indicator 2117 may also displaythe corresponding color.

Assuming that upon actuator 2124 being actuated by a user from controlinterface 2110 or 2130, for example, that the control applicationinitially displays control interface 2140 as shown in FIG. 11J and thatthe lighting load is producing a blue based color at that time, forexample, as a user touches or activates a mouse over pallet 2145, forexample, the control application may display actuator 2142 and controllines 2144 a and 2144 b at a point relative to the activation point.Thereafter, the control application may move the actuator 2142 andcontrol lines 2144 a and 2144 b according to the user action as shown inFIG. 11K (assuming the user move the actuator 2142 towards an orangebased color, for example). As the user moves actuator 2142 over pallet2145 to set the lighting load to a new color point within pallet 2145,the control application may display an indicator (not shown in FIG. 11K)together with the actuator. The indicator may display a numerical valuethat corresponds to chromaticity coordinates (such as x and ycoordinates) of the color point the actuator is set to, for example,although other values may be used. As the user moves the actuator 2142over pallet 2145, the control application may dynamically update thisindicator to correspond to the setting of the actuator. In addition andas shown in FIG. 11K, as the user moves the actuator 2142 over thepallet 2145, the control application may dynamically update indicator2117 to correspond to the color at which the actuator 2142 is currentlyset to. According to a further example and as shown in FIG. 11K, thecontrol application may also increase the size of indicator 2117 (inthis example, indictor 2117 is shown as a circle where the weight of theline forming the circle is heavier or larger or thicker in FIG. 11K ascompared to FIG. 11J for example). In this fashion, the controlapplication may provide an additional mechanism to show the user thecolor the lighting load is being set to. According to a still furtherexample, at a set time duration after which the user stops actuatingactuator 2142 and/or upon the user no longer selecting the actuator, thecontrol application may return indicator 2117 to a smaller size/lighterweight, as shown in the example of FIG. 11L, continuing to show actuator2142 and control lines 2144 a and 2144 b at the new color point, forexample. One will recognize that rather than increase the size ofindicator 2117 as actuator 2142 is moved in order to display a color tothe user, other mechanisms may be used to show the color to the user,such as by rendering actuator/icon 2116 in the color as the actuator isactivated.

According to a still further example, assuming the lighting load is offwhen a user selects actuator 2124 thereby causing control interface 2140to be displayed by the control application, a user selecting pallet 2145(e.g., via mouse or touch) may cause the lighting load to turn on (suchas to full intensity, to an intensity to which the lighting load waspreviously set to, or to a preferred intensity level of the user, etc.),and with the appearance of actuator 2116 changing to an on state,indicator 2117 being displayed, and with actuator 2112 being displayedat the present intensity level. Similarly, actuator 2142 and controllines 2144 a and 2144 b may appear at a location relative to where theuser touches pallet 2145 and/or at a location relative to the color thelighting load was previously set to, or to a preferred color value ofthe user, although other examples are possible and with the lightingload being controlled to this color (again, with indicator 2117 alsoindicating the color). Thereafter, a user may move actuator 2142 asdescribed above.

As similarly discussed above, based on detecting the selection/movementof actuator 2142, the control application may communicate one or moremessages to the system controller 250 a, for example, to instruct thecontroller to reconfigure the lighting control device/lighting load(s)based on the user's instructions.

As shown in FIG. 11M, while the lighting load is set to a color pointusing control interface 2140, a user may also actuate from controlinterface 2140 any of actuators 2112, 2114 a, and/or 2114 b to controlthe dimming state/intensity of the lighting load. Again, as this occurs,the control application may increase the intensity of indicator 2119 asshown in FIG. 11M. Similarly, as shown in FIG. 11N, while the lightingload is set to a color point using control interface 2140, a user mayalso actuate from control interface 2140 the “Vibrancy” actuator 2122 toconfigure the lighting control device/lighting load to enter vibrancymode. As indicated above, vibrancy mode may not change (or substantiallychange) the color point/chromaticity coordinates of the color beingproduced by the lighting load, but may alter the contribution of each ofthe RGBW LEDs in generating the colored light, which may includereducing the intensity/contribution of the white LED(s) for example,thereby making certain objects in a space more vibrant. In response todetecting selection of the vibrancy actuator 2122, the controlapplication may display the appearance of actuator 2122 to show it isactivated, as shown in FIG. 11N and communicate one or more messages tothe system controller 250 a, for example, to instruct the systemcontroller to configure the lighting control device/lighting load toenter a vibrancy mode. While the “Vibrancy” actuator 2122 is activatedand a user modifies the color and or intensity of the lighting load viacontrol interface 2140, the color rendered by the lighting load maycontinue to be in the “vibrant” state/vibrancy mode. Similarly, a usermay deactivate vibrancy mode from control interface 2140 thus returningto a normal setting (thus maintaining the color output of the lightingload, but increasing the contribution of the white LED(s) for example ascompared to when vibrancy mode is activated). Lastly, assuming a userturns the lighting load off (such as, for example, through any ofactuators 2116, 2112, 2114 a, and/or 2114 b) as described herein whilecontrol interface 2140 is displayed, the control application mayautomatically display control interface 2110 as shown in FIG. 11C. Onewill recognize that other examples are possible. One will also recognizethat actuator 2120 may be activated from control interface 2140,resulting in the control application displaying control interface 2130for example.

According to another example with respect to vibrancy control via the“Vibrancy” actuator 2122 and pallet 2145 that allows a user to configurea lighting load to any of a plurality of colors that lie within thepallet, vibrancy control may be limited to colors that are within apredefined range of colors within the pallet. For example, referring tothe color palette 2245, the vibrancy control may be limited to apredefined set of colors on the right side of the palette (i.e., whitecolors). The predefined colors may be the 10% or 20% of colors on theright side of the palette. The “Vibrancy” actuator 2122 and thusvibrancy control may be disabled when the user selects colors in thepalette that are outside of this predefined set of colors, as it may notbe possible to render these colors in multiple ways using, for example,different intensities of RGB and white LEDs. Assuming a lighting loadincludes additional LEDs, for example, of other colors, a broader rangeof pallet 2245 may allow actuation of the “Vibrancy” actuator 2122.

One will recognize that if a lighting control device/lighting load is invibrancy mode when the control application displays any of controlinterfaces 2110, 2130, or 2140, for example, the “Vibrancy” actuator2122 may be shown as being activated.

Referring now to a further example with respect to “Vibrancy” actuator2122, upon detecting selection of this actuator by a user the controlapplication may display to a user an interface (not shown) that mayinclude, for example, three actuators labeled for example, “High”,“Low”, and “Cancel”. Selection of “Cancel” by a user may cause thecontrol application to close the interface and return the user to thecontrol interface from which the “Vibrancy” actuator 2122 was selected.Upon detecting that a user has selected the “High” actuator, the controlapplication may communicate one or more messages to the systemcontroller 250 a, for example, to instruct the system controller toconfigure the lighting control device/lighting load to enter a vibrancymode (or a “high” vibrancy mode, or an “on” setting). Vibrancy modeaccording to this example may include setting the lighting load toproduce light at 3000K, for example (although other color temperaturesmay be used) and to set the intensity of the lighting load to 100%(although other intensities may be used). In this mode, generating lightat 3000K may include generating the color with the red, green, and/orblue LED(s) for example, and reducing the intensity/contribution of thewhite LED(s) for example (as compared to when the “Low” actuator isselected) (e.g., setting the intensity of the white LEDs to 0%), therebymaking certain objects in a space more vibrant. Upon selection of the“High” actuator, the control application may again display the controlinterface from which the “Vibrancy” actuator 2122 was selected, withactuator 2116 set to show the lighting load is “on”, with indicator 2117set to a color to correspond to 3000K, and with “Vibrancy” actuator 2122set to show that vibrancy mode is activated (e.g., as shown in FIG.11D). If the “Vibrancy” actuator 2122 was selected from controlinterface 2130, the control application may show actuator 2132 at aposition along control line 2135 c/pallet 2135 that corresponds to3000K. If the “Vibrancy” actuator 2122 was selected from controlinterface 2140, the control application may show actuator 2142 andcontrol lines 2144 a and 2144 b at a position in pallet 2145 thatcorresponds to 3000K. Assuming a user next changes the color beingproduced by the lighting load via control interface 2130 or 2140, thecolor produced by the lighting load may still be produced in “High”vibrancy mode, i.e., a reduced intensity/contribution of the whiteLED(s) for example (as compared to the “Low” vibrancy mode).

As an alternative, upon detecting that a user has selected the “Low”actuator, the control application may communicate one or more messagesto the system controller 250 a, for example, to instruct the systemcontroller to configure the lighting control device/lighting load toenter a non-vibrancy mode (or a “low” vibrancy mode, or an “off”setting, or to a normal setting). Non-vibrancy mode according to thisexample may include setting the lighting load to produce light at 3000K,for example (i.e., a same color temperature as the “High” mode” althoughother color temperatures may be used) and to set the intensity of thelighting load to 100% (i.e., a same intensity as the “High” mode”although other intensities may be used). In this mode, as compared tothe “High” vibrancy mode, generating light at 3000K may includegenerating the color with the red, green, and/or blue LED(s) forexample, and using an increased intensity/contribution of the whiteLED(s) for example, thereby making certain objects in a space lessvibrant (as compared to High vibrancy mode). Upon selection of the “Low”actuator, the control application may again display the controlinterface from which the “Vibrancy” actuator 2122 was selected, withactuator 2116 set to show the lighting load is “on”, with indicator 2117set to a color to correspond to 3000K, and with “Vibrancy” actuator 2122set to show that vibrancy mode is de-activated (e.g., as shown in FIG.11A). If the “Vibrancy” actuator 2122 was selected from controlinterface 2130, the control application may show actuator 2132 at aposition along control line 2135 c/pallet 2135 that corresponds to3000K. If the “Vibrancy” actuator 2122 was selected from controlinterface 2140, the control application may show actuator 2142 andcontrol lines 2144 a and 2144 b at a position in pallet 2145 thatcorresponds to 3000K. Assuming a user next changes the color beingproduced by the lighting load via control interface 2130 or 2140, thecolor produced by the lighting load may still be produced in “Low”vibrancy mode, i.e., an increased intensity/contribution of the whiteLED(s) for example (as compared to the “High” vibrancy mode). One willrecognize that other variations are possible.

Referring now to FIG. 11O there is shown another example controlinterface 2150. Control interface 2150 may be similar to, and operatesimilar to, control interfaces 2110, 2130, and 2140 for example. Forexample, control interface 2150 may include an actuator 2116 forcontrolling/indicating the on/off state of a lighting controldevice/lighting load as described herein, and may include an indicator2117 for indicating the color a lighting load is currently configured toproduced, as described herein. Control interface 2150 may furtherinclude actuators 2112, 2114 a, and 2114 b, for example, for controllingthe intensity level of a lighting load as described herein. Controlinterface 2150 may further include “Warm/Cool” actuator 2120 and “FullColor” actuator 2124 as described herein. As one example, actuation of“Warm/Cool” actuator 2120 may cause the control application to displayin control interface 2150 a pallet 2135 together with actuators 2112,2114 a, and 2114 b, for example (as shown in FIG. 11O). Actuation ofactuator 2132 by a user may allow a user to configure the lighting loadto produce a color along the black body curve, for example, as describedherein, with indicator 2117 indicating that color as described herein.Similarly, actuation of “Full Color” actuator 2124 may cause the controlapplication to display in control interface 2150 a pallet 2145 togetherwith actuators 2112, 2114 a, and 2114 b, for example (similar to controlinterface 2140). Actuation of actuator 2142 of pallet 2145 by a user mayallow a user to configure the lighting load to produce any of aplurality of colors within a color gamut, for example, as describedherein, with indicator 2117 indicating that color as described herein.

According to a further aspect of this example, control interface 2150may include a “More” actuator 2151 (shown in FIG. 11O together withpallet 2135). The “More” actuator 2151 may also be shown when pallet2145 is displayed in control interface 2150. Upon detecting selection ofactuator 2151, the control application may expand control interface 2150to include an “Auto-Vibrancy” actuator 2152 as shown in FIG. 11P. Inthis example, control interface 2150 is scrolled upward as“Auto-Vibrancy” actuator 2152 is displayed, although other examples arepossible. A similar action may occur when the control application isdisplaying pallet 2145 and the “More” actuator 2151 is actuated.

The “Auto-Vibrancy” actuator 2152 (also referred to herein as an autoactuator) may be enabled and disabled by a user to enable/disable (e.g.,turn on/off) what may referred to as an “auto-vibrancy” feature asdescribed herein. In this example of FIG. 11P, the “Auto-Vibrancy”actuator 2152 is shown as being actuated/enabled, which may be thedefault state. According to this example, when the “Auto-Vibrancy”actuator 2152 is enabled (i.e., is on), the control application maycause (e.g., by communicating one or messages to the system controller250 a) the color rendering index (CRI) value for the lighting controldevice/lighting load to be automatically configured at the color thelighting control device/lighting load is configured to produce. Forexample, given a certain color point (whether selected via pallet 2135or pallet 2145, for example), the “Auto-Vibrancy” actuator 2152 beingenable may automatically configure the lighting load to increase the CRIvalue of the light being produced by the lighting load at that color tobe greater than or equal to a CRI threshold value, which may be greaterthan or equal to 90.

Specially, a light output of a lighting load may be measured by a colorrendering index (CRI) value. The CRI value may be a measurement of thelighting load's ability to reveal the actual color of objects ascompared to an ideal light source (e.g., natural light). A higher CRIvalue may be a desirable characteristic of a user. For example, alighting load with a higher CRI value may provide light such that theobjects within a space reflect light at a natural color. Assuming alighting load is an RGBW LED lighting load as described herein, forexample, each of the respective LEDs that are comprised within the RGBWlighting load may be defined by a certain CRI value. In addition, anRGBW lighting load, for example, itself may be defined by a CRI value(e.g., a CRI value that indicates a summary or average CRI of each ofthe respective LEDs comprised within the lighting load). CRI values maybe in the range of 0 to 100, inclusively. For example, the lowestpossible CRI value may be 0 and the highest possible CRI value may be100. Not all lighting loads may be configurable to all CRI values for agiven produced color. The control application may be used to configure aCRI value of a lighting load(s) at a given color. A CRI value greaterthan or equal to a threshold (e.g., a CRI value of 90) may be desirableand may be referred to herein as “optimal”, “optimized”, or “maximized”.That said, other ranges (e.g., smaller and/or larger ranges) may also beconsidered “optimal”, “optimized”, or “maximized”. Hence, as describedherein, the control application may increase or attempt to increase theCRI value of a lighting load at a given selected colors to a valuegreater than or equal to a threshold CRI value. For example, thethreshold CRI value may be 90. One will appreciate, however, that thethreshold CRI value may be other values. For example, the CRI thresholdvalue may be a value which may be considered a desirable threshold thata system may attempt to achieve given the certain characteristics of theload control system and/or lighting control devices (e.g., quality ofthe LEDs used in a lighting load). As described herein, optimizing theCRI value towards or above the threshold CRI value may be referred to asoptimizing the CRI value.

Hence, again, when the “Auto-Vibrancy” actuator 2152 is enabled, thecontrol application may automatically configure the lighting load (basedon determining that the actuator is enabled and by communicating one ormore messages to the system controller 250 a for example) such that theCRI value of the light output of the lighting load at a given selectedcolor is greater than or equal to a CRI threshold value, (e.g., greaterthan or equal to 90) (which may be referred to herein as optimizing theCRI value towards or greater than the CRI threshold value). In certaininstances (e.g., for a certain color point or CCT) the CRI value may beunable to be a value that is greater than or equal to the CRI thresholdvalue. In those instances, the “Auto-Vibrancy” actuator 2152 beingenabled may cause the lighting control device to increase the CRI valueof the light output of the lighting load towards (e.g., as close aspossible to) the CRI threshold value. As similarly described herein,when the “Auto-Vibrancy” actuator 2152 is enabled as determined by thecontrol application, as a user selects colors via pallets 2135 and/or2145, the control application, system controller, and/or lightingcontrol device may cause the CRI value of the light output of thelighting load to be optimized as the user makes changes (e.g., achieve aCRI value that is greater than or equal to 90).

According to a further aspect of this example, the “Auto-Vibrancy”actuator 2152 may be disabled by a user as shown in FIG. 11Q. Upondetecting/determining that a user has disabled actuator 2152, thecontrol application may further expand control interface 2150 to displayactuator 2153 (which may be referred to herein as a vibrancy actuatorfor example) that is movable/slide-able (e.g., vertically movable) alongcontrol line 2156, an increase actuator 2154 a and a decrease actuator2154 b.

As noted, actuator 2153 may be movable/slide-able (e.g., a verticallymovable, although one will recognize that actuator 2153 mayalternatively be horizontally moveable, for example) along control line2156 and may allow a user to increase the relative vibrancy/vibrancylevel of the light being output by a lighting load (e.g., by moving theactuator vertically upward towards position 2155 a) or decrease thevibrancy/vibrancy level of the light being output by a lighting load(e.g., by moving the actuator vertically downward towards position 2155b). As similarly described herein, altering the vibrancy of a givenlighting load may cause the color of the light produced by a lightingload to remain the same or substantially the same, but may alter thecontributions of the individual LEDs making up that light to makeobjects more or less vibrant. Actuator 2153 may allow a user to controlthe vibrancy/vibrancy level of the lighting load from a relative maximumlevel such as 100% (position 2155 a) to a minimum level such as 0%(position 2155 b). Hence, as actuator 2153 is moved towards position2155 a, an object may become increasingly more vibrant and similarly, asactuator 2153 is moved towards position 2153 b, an object may becomedecreasingly less vibrant. The control application may display theposition of actuator 2153 along control line 2156 to represent thecurrent relative vibrancy level of the lighting load. The controlapplication may also display with actuator 2153 an indicator 2157 thatnumerically represents the current vibrancy level of the lighting load,here shown as a numerical percentage value 50% although other examplenumerical representations may be used. The control application may alsodynamically vary the value of indicator 2157 as the user moves actuator2153 vertically upward and downward. As also shown in FIG. 11Q, theportion of control line 2156 that lies below the actuator 2153 may beshown in a different intensity or line thickness, for example (here agreater intensity/line thickness) than the portion of the control line2156 that lies above the actuator 2153

Similar to actuator 2153, increase actuator 2154 a and decrease actuator2154 b may also enable a user to increase and decrease, respectively,the vibrancy of the lighting load. As one example, each of actuators2154 a and 2154 b may be selectable in a single action (e.g., by a clickand release of a mouse button, or a touch and release of the displayscreen of network device 680). Here, each individual actuation ofincrease actuator 2154 a may increase the vibrancy of the lighting loadby a defined amount (e.g., 1%) and similarly, each individual actuationof decrease actuator 2154 b may decrease the vibrancy of the lightingload by a defined amount (e.g., 1%). The defined amount may be userdefinable. As another example, each of actuators 2154 a and 2154 b maybe selectable for a prolonged duration (e.g., by a press and prolongedrelease of a mouse button, or a prolonged touch of the display screen ofnetwork device 680). Here, the actuation may cause the vibrancy level toincrease/decrease until the mouse button is released or the touch of thescreen is removed, for example. According to one example, as a userselects the increase actuator 2154 a or the decrease actuator 2154 b,the control application may also automatically move actuator 2153 in theup or down direction, respectively, and update the value of indicator2157 accordingly. Upon disabling “Vibrancy-Actuator” 2152, the controlapplication may position actuator 2153 along control line 2156 torepresent the current vibrancy level of the lighting load, and mayconfigure the value of indicator 2157 accordingly. One will recognizethat as a user alters the vibrancy level, the CRI value of a light loadmay move below the CRI threshold value.

According to one example, when “Vibrancy-Actuator” 2152 is disabled,actuators 2153, 2154 a, and 2154 b may only be enabled when the controlinterface 2150 is displaying pallet 2135. When the control interface isdisplaying pallet 2145 for example, vibrancy control via actuators 2153,2154 a, and 2154 b may be disabled. Alternatively, when the controlinterface is displaying pallet 2145, vibrancy control via actuators2153, 2154 a, and 2154 b may be limited to colors that are within apredefined range of the color gamut. For example, referring to the colorpalette 2145 vibrancy control may be limited to a predefined set ofcolors on the right side of the palette (i.e., white colors). Thepredefined colors may be the 10% or 20% of colors on the right side ofthe palette. Actuators 2153, 2154 a, and 2154 b and thus vibrancycontrol may be disabled when the user selects colors in the palette thatare outside of this predefined set of colors, as it may not be possibleto render these colors in multiple ways using, for example, differentintensities of RGB and white LEDs. Assuming a lighting load includesadditional LEDs, for example, of other colors, a broader range of pallet2245 may allow for vibrancy control via actuators 2153, 2154 a, and 2154b.

Again, as similarly described herein, as a user changes the color of alighting load via pallet 2135 and/or pallet 2145 (or a portion thereof)for example, the control application may cause the lighting load (viamessages communicated to the system controller 250 a for example), toproduce light with a vibrancy level based on the setting of actuator2153. Similarly, assuming “Vibrancy-Actuator” 2152 is disabled and auser selects a desired vibrancy level (at a selected color) via actuator2153 for example (thereby causing a lighting load to render light atthat color and vibrancy level), upon the control application detectingthe “Vibrancy-Actuator” 2152 being enabled, the control application maycommunicate one or more messages to system controller 250 a. Forexample, to cause the lighting control device/lighting load to alter thelight output of the lighting load such that the CRI value of the lightoutput/lighting load is greater than or equal to the CRI thresholdvalue. Other examples are possible.

One will recognize that the example control interfaces shown in FIGS.10A-10C and FIGS. 11A-11Q may be activated from other graphical userinterfaces, including for example, other graphical user interfacesdescribed herein, including, for example, the control interfaces beingactivated from an icon representing a lighting control device that iscurrently in an off state (as compared to selecting an icon frominterface 702 that shows control device in an on state).

Returning to FIG. 6C, once a user is done with interface 702, the usermay select icon 714 (the “Done” icon although icons may be used). Upondetecting/determining that the user selected icon 714, the controlapplication may once again display interface 610 to the user, as shownin FIG. 6A.

Turning now to icon 624 of FIG. 6A, as indicated this icon may be ashades devices icon that indicates to the user the number of shadedevices with respective shades within the load control system 210 a thatare currently open/up (where open/up may be any shade state other than afully closed position) (One will recognize that while shades icon 614 isdiscussed herein as being associated with shades, it may also beassociated with drapes, curtains, or blinds, for example, and othertypes of window coverings. Alternatively, section 620 may include othericons for such devices.) Similar to lighting control devices, a givenshade device may control more than one shade (e.g., if multiple shadescovering several different windows are linked together as one) and maycontrol these shades in unison (or may possibly be configured toindividually control these shades to different states). According to oneexample, the control application may view a given shade device and itsrespective shades as one device. In this example, if multiple shadescontrolled by the shade device are in an open/up state, the controlapplication may count this as one (1) with respect to the numberassociated with icon 624, regardless of the number of shades that areactually controlled by the device. Nonetheless, one will recognize thatthe number associated with icon 614 may represent the actual number ofshades controlled by each lighting control device. Here, the controlapplication may view each shade controlled by a given shade deviceindividually. In this example, the number associated with icon 624 maybe representative of each shade. Hence, if two shades controlled by ashade device are in an open/up state, the control application may countthis as two (2) with respect to icon 624. For description purposes, thecontrol application is described herein from the perspective of a shadedevice, where the shade device and its respective shades are treated asa single unit. The control application may determine the number ofshades that are currently open/up based on information obtained from thesystem controller 250 a. In this example, the control application hasdetermined based on information received from the system controller 250a that three shade devices have respective shades currently open/up(where open/up may include a shade in a partially open/up state). Again,the control application and/or the system controller may perform thecount to determine this number, for example. The control application mayindicate this determination to the user through the displayed number “3”associated with the icon 624 as shown in FIG. 6A, although again, thecontrol application may display the number in other fashions. Inaddition to displaying the number of shade devices with shadesdetermined to be currently open/up, as similarly discussed with lightingcontrol devices icon 622, the control application may actively updatethe count displayed by icon 624 based on, for example, the systemcontroller 250 a actively monitoring the state of shades in the userenvironment (e.g., as a result of a user in the environment raising andlowering the shades for example) and report this information to thecontrol application either asynchronously and/or as a result of thecontrol application requesting from system controller 250 a the statusof the control devices/shades, for example. In this fashion, icon 624may allow a user to quickly and easily determine from network device 680whether any shades are open/up in the user environment. If no shades aredetermined to be currently open/up, the control application may displaythe value “0” with icon 624, may display no value with the icon, may notdisplay the icon at all (thereby indicating no shades are open/up,etc.). Other variations are possible. For example, rather thandisplaying a number with icon 624, the control application may displaythe icon when any shades are open/up and not display the icon when allshades are down/closed. As a still further example, icon 624 mayindicate the number of shades that are currently down/closed.

Icon 624 may also be selectable by the user. Upon detecting/determiningthat the user has selected icon 624, the control application may displayto the user via network device 680 graphical user interface 720 as shownin FIG. 6F. Interface 720 may continue to display to the user the icon624 and the number of shade devices with shades currently determined tobe open/up. Interface 720 may also include an “Open All” icon 724(although other text and/or icons may be used) and/or may also include a“Close All” icon 726 (although other text and/or icons may be used),both of which may be selectable by the user. Interface 720 may alsoinclude a respective icon 716 for each shade device having a respectivecontrolled shade that is currently open/up (Again, according to thisexample, the control application may be configured to treat a shadedevice and its respective shade(s) as one unit, collectivelyrepresenting the unit as one icon. As an alternative, each shadecontrolled by a shade device may be represented by an icon in interface720, or some combination thereof). Each of these icons 716 may also beselectable by the user. In this example, three icons 716 are shown inconnection with the value “3” as shown with icon 624. According to afurther and/or alternative example and as shown in FIG. 6F, interface720 may also include a respective icon 718 (here three are shown) foreach shade device in the load control system where its respectivecontrolled shade(s) is currently closed/down. Each of these icons 718may also be selectable by the user. The control application may providea visual indication to a user as to the state of all shades in the loadcontrol system. Assuming the control application is configured tooperate as in FIG. 6F (i.e., both icons 716 and 718 being shown), thecontrol application may use one or more visual tools/indicators indisplaying the respective icons 716 and 718 to indicate which shadedevices of the load control system have shades that are open and whichhave shades that are closed. As one example, the control application maychange the appearance of the icons for open shades vs closed shades,such as using different colors and/or contrast between the icons as inthe example of FIG. 6F. As another and/or additional example, thecontrol application may use different icons for open shades vs closedshades. In one example, icons representing open shades may have iconsshowing partially open shades and icons representing closed shades mayhave icons showing closed shades. Other examples are possible.

Similar to the lighting control devices of FIG. 6C, the controlapplication may also use the location indicator and/or type indicator todisplay with each icon 716 and 718 an indication of the respective shadedevice's/shade's location and/or function in the user environment (inthis example, textual information such as, “Kitchen Left Shade,”“Kitchen Center Shade,” “Kitchen Right Shade,” “Living Room Left Shade,”“Living Room Center Shade,” and “Living Room Right Shade” are used,although other mechanisms are possible such as segregating icons bylocation, similar to section 660 of FIG. 6A).

Similar to the lighting control devices of FIG. 6C, the controlapplication may actively update icons 716 and 718 in user interface 720as the respective shades in the user environment change state. Forexample, if the ‘Kitchen Left Shade” is moved from an openstate/position to a closed state/position by a user in the kitchen, thecontrol application may receive an indication of this change from thesystem controller 250 a (for example, automatically or in response to aquery by the control application) and change the respective icon indisplay 720 to have the appearance of an icon as represented by icons718. In addition, the control application may decrement the countassociated with icon 624. Similarly, if the ‘Living Room Left Shade” ismoved from a closed state/position to an open state/position by a userin the kitchen, the control application may receive an indication ofthis change from the system controller 250 a and change the respectiveicon in display 720 to have the appearance of an icon as represented byicons 716. In addition, the control application may increment the countassociated with icon 624.

Turing now to icon 724 of user interface 720, it may allow a user toopen all shades within the load control system 210 a. Upondetecting/determining that the user selected icon 724, the controlapplication may communicate one or more messages to the systemcontroller 250 a instructing the system controller to open all shades.Once completed, the system controller 250 a may provide a response tothe control application (either automatically or in response to a queryby the control application, for example) indicating that the shades arenow open. According to one example, “opening” all shades may result inthe system controller controlling each shade to its respective fullyopen state. According to another example, the system controller, mayexample, may store for each shade a defined position (e.g., a userdefined position) the shade should be moved to in response to an “OpenAll” request. Other variations are possible. In response, the controlapplication may display an example interface as shown in FIG. 6G.Specifically, the control application may change the number valueassociated with icon 624 to indicate a new number of shade deviceshaving respective shades that are open (6 in this example), and maychange the appearance of icons 716/718 as necessary to represent openshades (in the example of FIG. 6G, all shade icons 716/718 are shown asopen shades). Note that in FIG. 6G icon 724 may be deactivated by thecontrol application since all shades are open (where deactivating mayinclude making the icon 724 non-selectable by a user and/or changing theappearance of icon 724 such as by changing its color or contrast ascompared to other icons, removing the icon from interface 720, etc.). Ifa shade is subsequently closed (such as by a user in the userenvironment 202 a closing a shade), in addition to decrementing thenumber associated with icon 624 to “1” for example, and changing an iconin interface 720 accordingly to show a closed shade, the controlapplication may also activate/re-activate icon 724 (where activating theicon may include making the icon selectable by a user and/or changingthe appearance of icon 724 such as by changing its color or contrast ascompared to other icons, displaying the icon in interface 720, etc.). Asfor icon 726, it may allow a user to close all shades within the loadcontrol system 210 a. Upon detecting/determining that the user selectedicon 726, the control application may communicate one or more messagesto the system controller 250 a instructing the system controller toclose all shades. Once completed, the system controller 250 a mayprovide a response to the control application (either automatically orin response to a query by the control application, for example)indicating that all shades are now closed. In response, the controlapplication may display an example interface as shown in FIG. 6H.Specifically, the control application may change the number valueassociated with icon 624 to “0” for example or show no value at all ashere, and may change the appearance of icons 716/718 as necessary torepresent closed shades (in the example of FIG. 6H, all shade icons716/718 are shown as closed shades). Note that icon 726 may bedeactivated by the control application since all shades are closed. If ashade is subsequently opened (such as by a user in the user environment202 a opening a shade), in addition to incrementing the numberassociated with icon 624 to “1” for example, and changing an icon ininterface 720 accordingly to show an opened shade, the controlapplication may also activate/re-activate icon 726. One will recognizethat upon initially displaying interface 720 upon a user selection icon624 from interface 610, the control application may activate/deactivateicons 724 and 726 depending upon the open/close state of shades in theload control system 210 a.

As an alternative to selecting icons 724 and/or 726, a user may selectany of icons 716/718 to individually control the shade devices and thusshades. Upon detecting/determining that the user selected a given one ofthe icons 716/718, the control application may display to the user aninterface to control the respective shade device and thus shade(s). Forexample, assuming the control application detects/determines that theuser selects in interface 720 the icon 716 labeled “Kitchen Left Shade,”the control application may display the control interface 728 shown inFIG. 6I (in this example, if there is more than one shade controlled bythe control device, the shades may be controlled to a common state).Control interface 728 may be shown alone or superimposed over interface720, for example. One will recognize that control interface 728 is anexample and other controls are possible. Here, control interface 728 isshown with a vertically movable/slide-able actuator 730 that may beactuated by the user (again, the control application may determine,based on information provided by the system controller (e.g., from thetype indicator), an appropriate control interface to display to the userto control the selected device based on capabilities of the device). Thecontrol application may display the actuator 730 as in this example toprovide an indication to the user of the respective shade's position(i.e., the actuator is approximately mid-way along its possible path torepresent the shade(s) is partially closed/down, for example). Based ondetecting movement of the actuator 730 by the user (such as raising orlowering the shades, etc.), the control application may communicate oneor more messages to the system controller 250 a to instruct the systemcontroller to reconfigure the “Kitchen Left Shade” based on the user'sinstructions. If the user closes the shade(s), this update may bereflected in icon 624 (e.g., the number value displayed beingdecremented) and in interface 720 (e.g., the appearance of the icon) assimilarly discussed above. Similarly, if a shade(s) is initially closedand is now opened via actuator 730, this update may be reflected in icon624 (e.g., the number value displayed being incremented) and ininterface 720 (e.g., the appearance of the icon) as similarly discussedabove. As shown in FIG. 6I, control interface 728 may also include aselectable “Edit” icon 732 that when selected, may cause the controlapplication to display a user interface that will allow a user toreconfigure parameters associated with the Kitchen Left Shade. A usermay exit control interface 728 by touching an area of the display screenof network device 680 outside of the interface 728. Other examples arepossible.

Again, user interface 720 of FIG. 6F is one example. As another example,upon detecting that a user selected icon 624, the control applicationmay only display in graphical interface 720 a respective icon 716 foreach shade device having a respective shade that is currently open/upand may only include a “Close All” icon 726 to close the respectivelyopen shades (i.e., interface 720 may not include icons 718 representingcurrently closed shades and/or control icon 724). As another example, asindicated above shades icon 624 may alternatively show the number ofshades that are currently closed/down. In this example, upon detectingthat a user selected icon 624, the control application may only displayin graphical interface 720 a respective icon 718 for each shade devicehaving a respective shade that is currently closed/down and only includethe “Open All” icon 724 to open the respectively closed shades (i.e.,interface 720 may not include icons 716 representing currently openshades and/or control icon 726). Further examples are possible. Forexample, interface 720 may operate as shown in FIG. 6F with icon 624showing the number of open shades, and both icons 716 and 718 present toshow the status of all shades. However, interface 720 may not includethe “Open All” icon 724 and/or the “Close All” icon 726.

Returning to FIG. 6F, once a user is done with interface 720, the usermay select icon 722 (the “Done” icon although icons may be used). Upondetecting/determining that the user selected icon 722, the controlapplication may once again display interface 610 to the user, as shownin FIG. 6A.

Turning now to icon 626 of FIG. 6A, as indicated this icon may be athermostat devices icon that indicates to the user a current temperaturein the user environment 202 a. In particular, load control system 210 amay include one or more thermostat devices that control respective HVACsystems. The control application may determine a current temperature inthe user environment 202 a using information obtained from the systemcontroller 250 a based on the system controller's interactions with thethermostat device(s). Based on the current temperature(s) obtained fromthe system controller, the control application may determine arepresentative temperature reading for the user environment and indicatethis reading to the user by displaying/associating this reading (in thisexample, 72 degrees) with the icon 626 as shown in FIG. 6A. As oneexample, when the load control system includes a single HVAC system, thecurrent temperature indicated by the control application through icon626 may be the current temperature as measured by the correspondingthermostat device. When the load control system includes two or moreHVAC systems, the current temperature indicated by the controlapplication through icon 626 may be the current temperature indicated byone of the thermostat devices, the choice of which by the controlapplication may be based on information received from the systemcontroller as which to use, and/or information associated with therespective thermostat devices. For example, assuming the userenvironment has a downstairs and an upstirs HVAC system, the controlapplication may always use the current temperature indicated by thedownstairs thermostat, may use the current temperature indicated by thedownstairs thermostat during the day (e.g., where “day” may be providedby the system controller, such as 6 AM to 8 PM), and use the currenttemperature indicated by the upstairs thermostat during the evening(e.g., where “evening” may be provided by the system controller, such as8 PM to 6 AM), etc. Other variations are possible including the controlapplication allowing a user to select which of the thermostat devices touse and possibly when (one example of this is discussed in reference toFIG. 6K). As another example, the control application may use an average(as determined by the control application and/or system controller forexample) of the respective current temperatures as measured by therespective thermostat devices of each HVAC system. One will recognizethat other mechanisms and/or mathematical formulas may be used todetermine the temperature associated with icon 626 when there aremultiple HVAC systems. As a further example (not shown in the Figures),in addition to associating/displaying a current temperature with icon626 the control application may also display an indication of thecurrent heat and/or cool setpoint temperate to which a thermostat deviceis set to. When there are multiple thermostat devices/HVAC systems, thecontrol application may make a determination as to which setpointtemperate(s) to use in a similar fashion as the current temperature. Onewill recognize that the temperature values provided with icon 626 may bein Fahrenheit or Celsius, and may be configurable by the user.

For explanation purposes only, it will be assumed that the load controlsystem 250 a includes two HVAC systems (an upstairs and a downstairssystem) each with a respective thermostat device and that the controlapplication displays the current temperature reading of the downstairssystem with icon 626. In addition to displaying the current temperature,as with lighting devices icon 622 the control application may activelyupdate the current temperature displayed by icon 626 based on, forexample, the system controller 250 a actively monitoring the currenttemperature measured by the downstairs thermostat and reporting thisinformation to the control application either asynchronously and/or as aresult of the control application requesting from system controller 250a the status of the downstairs thermostat device, for example. In thisfashion, icon 626 may allow a user to quickly and easily determine fromnetwork device 680 a current temperature in user environment 202 a.

Icon 626 may also be selectable by a user. Upon detecting/determiningthat the user has selected icon 626, the control application may displayto the user via network device 680 a graphical user interface 740 asshown in FIG. 6J. Interface 740 may continue to display to the user icon626 and the current temperature reading. Interface 740 may also includea “Raise All” icon 744 (although other text and/or icons may be used)and/or may also include a “Lower All” icon 746 (although other textand/or icons may be used), both of which may be selectable by the userand may allow the user to control the thermostat devices of the loadcontrol system in tandem/together as discussed below. Interface 740 mayalso include a respective information section (also referred to hereinas a pane) for each thermostat device in the load control system. Inthis example with the load control system 210 a including two thermostatdevices, each device may have a respective information section or pane760 and 762 that provide respective status information and controls foreach thermostat device/HVAC system. In the event a load control systemhas more than two thermostat device/HVAC systems, the controlapplication may be configured to make information sections 760 and 762scrollable by the user (such as vertically scrollable) to displayadditional information sections or panes, one for each system. In oneaspect, information sections 760 and 762 allow a user to control therespective thermostat devices separately. As further shown in FIG. 6J,control application may use the location indicator and/or type indicatorassociated with each thermostat device to display in connection witheach thermostat device in information sections or panes 760 and 762 anindication of the respective device's location in the user environment(in this example, textual information such as, “Downstairs Thermostat”and “Upstairs Thermostat” are used, although other mechanisms arepossible). In general, the control application's use of textualinformation may allow the user to more easily determine the actualthermostat device/HVAC system in the user environment the information insections 760/762 refer to.

Using information section or pane 760 as an example, the controlapplication may display for a thermostat/HVAC system a currenttemperature reading 750 (here, 72 degrees) as determined by therespective thermostat device. Again, as a respective thermostat devicedetermines a change in the current temperature reading in the userenvironment and the system controller 250 a reports this change to thecontrol application (automatically or in response to a query by thecontrol application for example), the control application may activelyupdate the current temperature reading 750 displayed to the user. Thecontrol application may also display the setpoint temperature(s) 756(here, 70 degrees) the respective thermostat device is configured tocontrol its respective the HVAC system to. Assuming the HVAC system hasfour modes including a heat mode, a cool mode, an auto mode and an offmode, none, one or more setpoint temperature(s) 756 may be shown. Forexample, if the thermostat is set to off, no set point temperature maybe shown. If the thermostat is set to heat mode or cool mode, onesetpoint temperature 756 may be shown representing the temperature theHVAC system is set to heat or cool to, respectively. If the thermostatis set to auto mode, two setpoint temperatures may be shown representingthe temperature the HVAC system is set to heat to and set to cool to.Indications may also be provided to the user as to which of the twotemperatures is the heat to temperature and which is the cool totemperature. The information section 760 may also include selectableicon controls 752 (two pairs if two set point temperatures are shown)that allow a user to adjust the setpoint temperature(s) 756 of thethermostat device. In this example, “+” and “−” controls are used torespectively raise and lower the setpoint temperature 756. One willrecognize that other control types may be used. Each actuation of the“+” control by a user may raise the setpoint temperature 756 by apredetermined number of degrees (such as one degree). Similarly, eachactuation of the “−” control by a user may lower the setpointtemperature 756 by a predetermined number of degrees (such as onedegree). Upon detecting/determining that the user selected one of therespective “+” and “−” controls of icon 752, the control application maycommunicate one or more messages to the system controller 250 ainstructing the system controller to adjust the setpoint temperature ofthe thermostat device. Changes in the setpoint temperature(s) may alsobe reflected in setpoint temperature(s) 756 of interface 740.

The information section 760 may also include a selectable “carrot” 758,for example. Upon detecting/determining that the user selected carrot758, the control application may expand information section 760 todisplay additional controls/information to the user as shown in userinterface 764 of FIG. 6K (again, the controls displayed by the controlapplication may be based on capabilities/functionality of the thermostatdevice as determined from information provided by the systemcontroller). According to this example, user interface 764 may includethree control sections that may allow a user to further control theDownstairs thermostat/HVAC system. These control sections may include amode control 766 that may allow a user to select any of a heat mode,cool mode, auto mode, and off mode for example of the HVAC system asdescribed above. The control application may display with the modecontrol 766 the current mode of the HVAC system (here, cooling) asdetermined from the system controller. The control sections may furtherinclude a fan control 768 that may allow a user to turn the HVAC fan onand off. The control application may display with the fan control 768the current fan setting of the HVAC system (here, On) as determined fromthe system controller. Assuming the thermostat device/HVAC system isprogrammable, the control sections may further include a schedulecontrol 770 that may allow a user to turn the schedule on and off. Thecontrol application may display with the schedule control 770 thecurrent schedule status (here, On) as determined from the systemcontroller. Upon detecting/determining that the user selected any one ofthese controls (e.g., by touching the word “HEAT,” or “AUTO,” or “OFF,”etc.), the control application may communicate one or more messages tothe system controller 250 a instructing the system controller toadjust/reconfigure the thermostat device. User interface 764 may furtherinclude a selectable “Edit” icon 756 that when selected, may cause thecontrol application to display a user interface that will allow a userto reconfigure the schedule of the thermostat device. For example, theuser may be able to adjust on/off times, heating and cooling setpointtemperatures, etc., with the control application communicating thisinformation to the system controller 250 a.

Turning again to FIG. 6J and the “Raise All” icon 744 and “Lower All”icon 746, these controls may allow the user to raise and lowerrespectively the setpoint temperature(s) 756 of the respectivethermostat devices of the load control system in tandem/together. Onewill recognize that other control types may be used. Each actuation oficon 744 by a user may raise the respective setpoint temperature(s) 756(which may be different for each thermostat) of each thermostat deviceby a predetermined number of degrees (such as one degree). Similarly,each actuation of icon 746 by a user may lower the respective setpointtemperature(s) 756 of each thermostat device by a predetermined numberof degrees (such as one degree). If an HVAC system is set to auto mode,both setpoint temperatures of that system may move in tandem, forexample. For example, assume that the downstairs thermostat device/HVACsystem (represented by section or pane 760) has a setpoint temperatureof 70 degrees and that the upstairs thermostat device/HVAC system(represented by section or pane 762) has a setpoint temperature of 74degrees. An actuation of icon 744 by a user may raise the setpointtemperature of the downstairs thermostat device/HVAC system to 71degrees and may raise the setpoint temperature of the upstairsthermostat device/HVAC system to 75 degrees (assuming each actuation oficon 744 makes a one-degree change). Similarly, again assuming that thedownstairs thermostat device/HVAC system has a setpoint temperature of70 degrees and that the upstairs thermostat device/HVAC system has asetpoint temperature of 74 degrees, an actuation of icon 746 by a usermay lower the setpoint temperature of the downstairs thermostatdevice/HVAC system to 69 degrees and may lower the setpoint temperatureof the upstairs thermostat device/HVAC system to 73 degrees (assumingeach actuation of icon 746 makes a one degree change). Upondetecting/determining that the user selected one of the respective icons744 and 746, the control application may communicate one or moremessages to the system controller 250 a instructing the systemcontroller to adjust the setpoint temperatures of the thermostatdevices. Changes in the setpoint temperatures may be reflected insetpoint temperature(s) 756 of each device.

With further reference to FIG. 6J, if a given user environment includestemperature devices of different types, the appearance of sections 760and 762 may be different for each temperature device. Again, the controlapplication may make this determination from information received fromthe system controller, for example, and/or for information stored at thenetwork device. According to a further aspect of the controlapplication, when load control system 250 a includes multiple HVACsystems, as noted above the temperature associated with icon 626 maycorrespond to one of the systems. According to one example, the controlapplication may use the temperature associated with the first or topthermostat device/HVAC system as shown in interface 740 (here, thethermostat device/HVAC system represented by section 760). According toa further aspect of the control application, a user may change the orderof sections 760 and 762 displayed in interface 740 (e.g., A user maytouch a given section for at least a defined period of time. Upondetecting the touching, the control application may active the sectionand allow the user to drag the section up or down, for example, to thuschange the ordering). Upon changing the order, the control applicationmay now have the temperature associated with icon 626 track the new topsection. One will recognize that the order in which the sections 760 and762 should be displayed and which of the sections icon 626 should trackmay be stored at the network device and/or the system controller. Onewill also recognize that other variations are possible, including forexample, the temperature associated with icon 626 tracking the last ofsections 760 and 762.

Once a user is done with interface 740, the user may select icon 742(the “Done” icon although icons may be used). Upon detecting/determiningthat the user selected icon 742, the control application may once againdisplay interface 610 to the user, as shown in FIG. 6A.

As indicated, section 620 of user interface 610 of FIG. 6A may alsoinclude other icons such as a fans icon 776 as shown in FIG. 6L that mayindicate to the user a status of fan devices within the load controlsystem 210 a, such as the number of fans that are currently on. Similarto lighting control devices, a given fan device may control more thanone fan and may control these fans in unison. According to one example,the control application may view a given fan device and its respectivefans as one device. In this example, as long as one fan controlled bythe fan device is in an on state, the control application may count thisas one (1) with respect to the number associated with icon 776,regardless of the number of fans that are actually controlled by thedevice. Nonetheless, one will recognize that the number associated withicon 776 may represent the actual number of fans controlled by each fandevice. Here the control application may view each fan controlled by agiven fan device individually. In this example, the number associatedwith icon 776 may be representative of each fan. Hence, if two fanscontrolled by a fan device are in an on state, the control applicationmay count this as two (2) with respect to icon 776. For descriptionpurposes, the control application is described herein from theperspective of a fan device, where the fan device and its respectivefans are treated as a single unit. The control application may determinethe number of fans that are currently on based on information obtainedfrom the system controller 250 a. Again, the control application and/orthe system controller may perform the count to determine this number,for example. In this example, the control application has determinedbased on information received from the system controller 250 a that twofan devices have respective fans that are currently on (where on mayinclude a fan at any speed other than off). The control application mayindicate this determination to the user through the displayed number “2”associated with the icon 776 as shown in FIG. 6L. In addition todisplaying the number of fan devices with respective fans determined tobe currently on, similar to lighting control devices icon 622 thecontrol application may actively update the number displayed with thefans icon 776 based on, for example, the system controller 250 aactively monitoring the state of fans in the user environment (e.g., asa result of a user in the environment adjusting the fans) and reportthis information to the control application either asynchronously and/oras a result of, for example, the control application requesting fromsystem controller 250 a the status of the fans and/or control devices ingeneral. In this fashion, the fans icon 624 may allow a user to quicklyand easily determine from network device 680 whether any fans are on inthe user environment. If no fans are determined to be currently on, thecontrol application may display the value “0” with icon 776, may displayno value with the icon, or may not display the icon at all (therebyindicating no fans are on, etc.). Other variations are possible. Forexample, rather than displaying a number with icon 776, the controlapplication may display the icon when any fan is on and not display theicon when all fans are off. As a still further example, icon 776 mayindicate the number of fan devices with respective fans that are all inthe off state.

Icon 776 may also be selectable by the user. Upon detecting/determiningthat the user has selected icon 776 from user interface 620, the controlapplication may display to the user via network device 680 the graphicaluser interface 772 as shown in FIG. 6M. Interface 772 may continue todisplay to the user icon 776 and the number of fan devices with fanscurrently determined to be on. Interface 772 may also include a “TurnAll Fans Off” icon 778 (although other text and/or icons may be used),which may be selectable by the user. Interface 772 may also include arespective icon 780 for each fan device that has respective fansdetermined to be on (Again, according to this example, the controlapplication may be configured to treat a fan device and its respectivefan(s) as one unit, collectively representing the unit as one icon. Asan alternative, each fan controlled by a fan device may be representedby an icon in interface 702, or some combination thereof). Each of theseicons may also be selectable by the user. In this example, two icons 780are shown in connection with the value “2” as shown with icon 776. Thecontrol application may use the location and/or type indicatorassociated with each fan device to display in connection with each iconan indication of the respective fan device's/fan's location in the userenvironment (in this example, textual information such as, “DownstairsBathroom Fan,” and “Master Bedroom Fan” are used, although othermechanisms are possible such as segregating icons by location, similarto section 660 of FIG. 6A but only displaying icons for devicescurrently on). Similar to interface 702, the control application mayactively update icons 780 displayed to the user as fans in the userenvironment change state from on to off and off to on. For example, as afan controlled by a fan device is turned on by a user in the userenvironment for example, the control application may receive anindication of this change from the system controller 250 a (for example,automatically or in response to a query by the control application) anddisplay to the user an additional icon 780 in interface 772 that isassociated with the fan device of the fan, and also increase the numbervalue by “1” shown by icon 776. Similarly, as a fan controlled by a fandevice is turned off, the control application may receive an indicationof this change from the system controller 250 a and remove frominterface 772 the icon 780 associated with the fan device or change theappearance of the icon (e.g., change its color or contrast as comparedto other icons) when all fans controlled by the fan device are off, assimilarly discussed above. Other variations are possible. For example,the control application may configure interface 772 similar to interface720 of FIGS. 6F-6H and show all fan devices in the load control system(both on and off), including the state of each fan device as similarlydescribed for shades, and also allow a user to control fan devices assimilarly described for shades in FIGS. 6F-6H. Turning now to icon 778,as indicated, this icon may be selectable by the user and may allow theuser to turn off all fan devices and thus fans that are currently on inthe load control system 210 a. Upon detecting/determining that the userselected the icon, the control application may communicate one or moremessages to the system controller 250 a instructing the systemcontroller to turn all the fans off. Once completed, the systemcontroller 250 a may provide a response to the control application(automatically or in response to a query, for example) indicating thatthe fan devices are now off. In response, the control application maychange the number associated with icon 776 to “0” for example (or showno value for example), and remove or change the appearance of icons 780from interface 772, for example. The control application may alsodeactivate icon 778 since all fan devices/fan are off (wheredeactivating may include making the icon non-selectable by a user and/orchanging the appearance of icon 778 such as by changing its color orcontrast as compared to other icons, removing the icon from interface772, etc.). Once a fan device returns to the on state (such as by a userin the user environment 202 a turning a fan on), in addition toincrementing the number associated with icon 776 to “1” for example, anddisplaying an icon 780 in interface 772 representing the fan device, thecontrol application may also activate/re-activate icon 778 (whereactivating the icon may include making the icon selectable by a userand/or changing the appearance of icon 778 such as by changing its coloror contrast as compared to other icons, displaying the icon in interface772, etc.). One will recognize that other examples are possible such asinterface 772 also/alternatively including a “Turn All Fans On” icon,which upon selection, may cause the control application to communicateone or more messages to the system controller to turn all fans in theuser environment to an on state (or a pre-programmed set of fans to anon state). Again, such an action by a user may cause the controlapplication to increment the number associated with icon 622 and todisplay respective icons 780 accordingly. Other examples are possible.

As an alternative to selecting icon 778, icons 780 may also beselectable by the user and allow the user to individually control thefan device and thus fan(s) associated with the icon. (One will recognizethat if the control application is configured to show icons 780 in afashion that indicates the respective fan device is off, the icon maycontinue to be selectable by the user to control the device.) Upondetecting detecting/determining that the user selected a given one ofthe icons 780, the control application may display to the user aninterface to control the respective fan device/fan(s).

For example, assuming the control application detects/determines thatthe user selected in interface 772 the icon 780 labeled “Master BathroomFan” (in this example, the fan device may control one respective fan),the control application may display the control interface 782 shown inFIG. 6N. Control interface 782 may be shown alone or superimposed overinterface 772, for example. One will recognize that control interface782 is an example and other controls are possible. The “Master BathroomFan” may be a multi-speed fan and as such, the control application(determining that the fan is a multi-speed fan such as from its typeindicator) may display a control interface 782 as shown here withmultiple fan speed actuators 784 that may be actuated by the user (i.e.,the control application may determine, based on information provided bythe system controller (e.g., from the type indicator), an appropriatecontrol interface to display to the user to control the selected fandevice/fan based on capabilities of the fan device/fan). The controlapplication may display the actuators 784 to provide an initialindication to the user of the current fan speed of the fan controlled bythe fan device (e.g., the low speed actuator is highlighted in thisexample). Based on the detecting selection of one of the actuators 784by the user, the control application may communicate one or moremessages to the system controller 250 a to instruct the systemcontroller to reconfigure the fan device based on the user'sinstructions. If the user turns the fan device/fan off, this update maybe reflected in icon 776 (e.g., by decrementing the count by 1) and ininterface 772 as discussed above by removing or altering the appearanceof the icon 780 corresponding to the “Master Bathroom Fan,” for example.As shown in FIG. 6N, control interface 782 may also include a selectable“Edit” icon 784 that when selected, may cause the control application todisplay a user interface that may allow a user to reconfigure parametersassociated with the respective fan device/fan. A user may exit controlinterface 782 by touching an area of the display screen of networkdevice 680 outside of the interface 782. Other examples are possible.

Returning to FIG. 6M, once a user is done with interface 772, the usermay select icon 774 (the “Done” icon although other icons may be used).Upon detecting/determining that the user selected icon 774, the controlapplication may once again display interface 610 to the user, as shownin FIG. 6A.

As indicated above, section 620 may show additional status informationthan that discussed herein. For example, the control application mayinclude in section 620 one or more icons to indicates alerts and/orsystem notifications, such as an indication of low batteries/a number oflow batteries in the load control system (assuming, for example, acontrol device(s) have batteries), an indication that an alarm is goingoff in the user environment 202 a (e.g., a smoke alarm, carbon monoxidedetector alarm, home security alarm), an indication of communicationerrors (e.g., that the system controller cannot communicate with one ormore control devices), etc. Any such icons may be selectable by a userresulting in the control application displaying to the user an interfacethat will provide additional information and/or system controls, forexample. Assuming the load control system includes occupancy sensors forexample, the control application may include in section 620 an iconproviding an indication of occupancy status in the user environment 202a. Such an icon may simply provide an indication of occupied/unoccupiedand/or may provide an indication of a number of people present in theuser environment 202 a. Selection of such an occupancy icon may causethe control application to display to the user an interface thatprovides additional information such as which rooms in the userenvironment are occupied and/or unoccupied assuming, for example, thatvarious rooms have occupancy sensors. One will recognize that thecontrol application may determine occupancy in other fashions such as bydetecting a change in status of control devices like lights, fans,shades, etc. from user actuated controls within the user environment, bysensors tracking doors opening/closing, etc. As another example, scenesmaintained by the system controller may include a “Vacation Mode,” an“Away Mode” (which may be a scene when occupants left home for the day),a “Home Mode” (which may be a scene when occupants have returned homefor the day), in addition to other scenes, etc. Accordingly, the controlapplication may include in section 620 one or more icons providing anindication as to which mode/scene is currently active in theenvironment. Selection of such an icon(s) may cause the controlapplication to display to the user an interface that allows, forexample, the user to change the mode/scene. Again, other examples arepossible.

Turning now to FIG. 6O and sections 640 and 660, upondetermining/detecting that a user has selected the Devices tab 642 (oras a default configuration), the control application may provide anindication that the tab is active (e.g., as shown by the under-bar 643,although other means may be used such as reverse highlighting, etc.) andmay display icons within information section 660 where the icons mayrepresent one or more of the control devices of the load control system210 a. According to one example, all control devices may be displayed insection 660. According to another example, certain control devices suchas thermostat devices or handheld/remote-control keypads configured toonly turn lighting load(s) on/off and/or to control the dimming levelsof the lighting loads, for example, may not be displayed in thissection. According to another example, the control application may beconfigurable by a user, thereby allowing a user to decide whether suchcontrol devices are to be shown in section 660. As indicated above, uponthe control application being started, it may default to the Devices tab642.

According to one example, when the Devices tab 642 is active, thecontrol application may subdivide section 660 into one or more panes(here three panes are shown, 802, 804, and 806). Each pane may representa location within the user environment 202 a. The control applicationmay determine the locations based on information received from thesystem controller 250 a, such as the location indicators associated withthe various control devices. The control application may provide anindication with each pane as to the location it represents. Here,textual labels are used, although other mechanism may also be used. Inthe example of FIG. 6O, the control application may label pane 802 as“Kitchen,” label pane 804 as “Living Room,” and label pane 806 as“Master Bedroom.” Within each pane 802, 804, and 806 the controlapplication may further display a respective icon (such as icons 810a-810 d) for control devices when the control device and/or the load(s)it controls are located within the respective location that the panerepresents. As shown, different icons may be used for different types ofcontrol devices. According to one example, icons for certain controldevices may appear in multiple panes 802, 804, and/or 806. As anexample, if a determination of whether to display in a certain pane anicon for a given control device is based on a location of the controldevice, the icon may appear in the one pane corresponding to thatlocation. If, however, a determination of whether to display an icon fora control device in a certain pane is based on a location of the loadsthe control device controls and those loads are in multiple locations,the icon may be displayed in each respective pane corresponding to thelocation. For description purposes the former example may be assumed.Other variations are possible. Again, the system controller may providean indication of the type of icon the control application should use foreach control device. As another example, the control application may useinformation provided by system controller on each control device todetermine which icon to use (e.g., for a fan type device use a fan icon,for a shade type device use a shade icon, for a lighting control deviceuse a light-based icon, for a keypad device use a keypad icon, etc.) Thecontrol application may further associate with each icon an indicationof the control device's and/or its respective load(s)' specificlocation/function as similarly discussed herein. For example, pane 802has three different displayed icons each with a respective textualidentifier (“Ceiling Lights,” Pendants,” and “Keypad.”). According to afurther aspect of interface 610, the order of panes 802, 804, and 806may be statically defined. According to a further aspect, the controlapplication may enable a user to change the order of panes 802, 804, and806 (e.g., A user may touch a given pane for at least a defined periodof time. Upon detecting the touching, the control application may activethe pane and allow the user to drag the pane up or down, for example, tothus change the ordering. Other variations are possible). One willrecognize that the order in which the panes 802, 804, and 806 are to bedisplayed may be stored at the network device and/or the systemcontroller. One will also recognize that other variations are possible.

The control application may initially display a maximum number of icons(here three, for example) in each pane. If a given location has morethan three control devices, the pane may include a “carrot” 808, forexample. Upon detecting/determining that the user has activated/selecteda carrot 808, the control application may expand the respective pane todisplay additional icons representing additional control devices in thelocation. Selection of the carrot 808 a second time may collapse thepane back to the three icons. As another example, the controlapplication by default may display in each pane all icons for allcontrol devices in a given location. Here, actuation of “carrot” 808 maycollapse the pane to show no icons and selection of the carrot 808 asecond time may expand the pane to show all icons. Other examples arepossible. Furthermore, section 660 may be scrollable (e.g., verticallyscrollable) to display additional panes representing additionallocations. According to one example, referring to FIG. 6P there is shownan example user interface with information section 660 scrolledrevealing another pane 808 corresponding to an “Office” location withinthe user environment 202 a and having respective icons representingadditional control devices located in the Office. In this example, assection 660 is scrolled to reveal additional panes below “MasterBedroom” pane 806, section 660 may expand, with section 620 scrollingoff of/being remove from the display interface of the network device andsection 660 consuming this space, and additional pane(s) (here pane 808)appearing below pane 806. Scrolling here may be referred to as scrollingdown or downward scrolling for discussion purposes only. This “downward”scrolling may be achieved for example by “swiping” one's fingervertically upward along interface 610, by selecting a downward pointingarrow, etc. as in known in the art. Continued “downward” scrolling ofsection 660 may cause the panes at the top of the section (here“Kitchen” pane 802) to disappear from section 660 and for additionalpanes to appear at the bottom (below “Office” pane 808) of the section660, assuming there are additional panes. Similarly, as section 660 isscrolled in the reverse direction (referred to herein as scrolling up,or upward scrolling for discussion purposes only, and which may beachieved for example by “swiping” one's finger vertically downward alonginterface 610, by selecting an upward pointing arrow, etc. as in knownin the art) to possibly reveal panes such as pane 802 that may have beenscrolled off of section 660, panes at the bottom of section 660 maydisappear from section 660 (such as pane 808) and additional panes mayappear at the top of section 660. Continued “upward” scrolling may causesection 660 to collapse as the top pane (here “Kitchen” pane 802) isreached, and for section 620 to be re-displayed, with interface 610 onceagain appearing as shown in FIG. 6O. According to another example,section 620 may not scroll off of the display interface 610 but rather,may be minimized as further discussed below with reference to FIGS. 7Aand 7B. According to another example, in addition to or as analternative to the above, selecting the Devices tab 642 (such as by“touching” or “tapping”) in the FIG. 6O configuration may cause section660 to expand and section 620 to disappear as shown in FIG. 6P. Again,section 660 may then be scrollable. Similarly, selecting the Devices tab642 (such as by “touching” or “tapping”) in the FIG. 6P configurationmay cause section 660 to collapse and section 620 to be re-displayed asshown in FIG. 6O.

According to a further aspect of the Devices tab 642, the controlapplication may display the icons in section 660 in a fashion to providean indication of the status/state of the corresponding control device assimilarly discussed herein. For example, the control application maychange the appearance of the icon (e.g., change its color and/orcontrast as compared to other icons) to signify the status/state of thecorresponding control device (and/or the state of its respectivecontrolled load(s)) as describe herein. For example, with respect tolighting control devices as represented by icons 810 a-810 d, icons 810a-810 b are shown in the example of FIG. 6O as indicating that thelighting load(s) of the corresponding control devices are on and icons810 c-810 d are shown in as indicating that the lighting loads of thecorresponding control devices are all off. Color and/or contrast may beused in a similar fashion for icons representing other types of controldevices. According to another example, different icons may be used for agiven type of device to represent different states, such as shown inFIG. 6F with icons 716 representing open shades and icons 718representing closed shades. Other examples are possible. According to afurther aspect of section 660, the control application may dynamicallychange the appearance of icons in section 660 as the state/status of thecorresponding control devices/loads change (e.g., if a light is turnedoff by a user in the user environment, the control application maychange the appearance of a lighting control device icon in section 660to show the changed state as similarly described herein). In general,the state/status of control devices as shown by the icons in section 660may match the status/state of control devices as represented by theicons in section 620 and the interfaces that correspond to these icons.

According to a further aspect of Devices tab 642, the icons shown insection 660 may be selectable by a user. Upon determining/detecting thata user has selected a given icon, the control application may display tothe user a control interface to control the respective device assimilarly shown and discussed with respect to FIGS. 6D, 6E, 6I, 6N,10A-10C, and/or 11A-11N for example.

As a further example, assume that icon 810 e of FIG. 6O represents akeypad control device having four buttons, for example, and that islocated in the Kitchen and that the keypad is configured to control oneor more control devices such as one or more lighting controldevices/lighting loads, shades, and speakers, and is programmed with aset of scenes (e.g., a set of buttons that each controls/configures arespective scene). These scenes may include, for example, an “Off” scenethat turns the lighting loads off, a “Dining” scene that sets thelighting loads, shades, and speakers to a predefined state for eating, a“Cooking” scene that sets the lighting loads and speakers to predefinedsettings conducive to cooking, and a “Bright” scene that sets thelighting loads to a fully on state. This is merely an example.Responsive to the control application determining/detecting that a userhas selected icon 810 e of FIG. 6O, the control application may displayto the user a control interface, such as control interface 812 of FIG.6Q. Using information provided by the system controller 250 a on thekeypad control device, the control application may display controlinterface 812 such that the interface is representative of the actualkeypad. For example, control interface 812 may have multiple selectablescene actuators 814 (here shown as buttons for example) eachrepresentative of and labeled as one of the scenes of the actual keypad.The control application may further display the actuators 814 to providean indication to the user as to the current scene setting of the keypad(i.e., here the “Dining” button is shown as selected, for example).Based on detecting/determining that a user has selected one of the sceneactuators 814, the control application may communicate one or moremessages to the system controller 250 a to instruct the controller toreconfigure the keypad/corresponding lighting loads, shades, and/orspeakers based on the user's instructions, thereby setting thecorresponding lighting loads, shades, and/or speakers of the Kitchen tothe selected scene. As further shown in FIG. 6P, control interface 812may also include a selectable “Edit” icon 816 that when selected, maycause the control application to display a user interface that may allowa user to reconfigure the scenes of the actual keypad control device(e.g., change one or more of the scene configurations) by communicatingone or more messages to the system controller 250 a. These changes mayalso be reflected in control interface 812. Before turning to the “Edit”icon, according to one example, if a given location (such as the Kitchenin this example) includes multiple keypad control devices that are allconfigured the same (e.g., each keypad includes the same number of scenebuttons and controls the same electrical loads, and actuation of thesame button on any given keypad results in the same scene across theloads), the control application may only display one icon 810 e in pane802 (according to this example), representing of all of the keypadcontrol devices. Editing the keypad as discussed below may result in thecontrol application/system controller reconfiguring each of the keypadcontrol devices within the load control system to the sameconfiguration. According to a further example, the control applicationmay display the keypad icon 810 e of pane 802 differently (e.g., changethe icons color and/or contrast) depending on whether a scene other thanthe Off scene is currently active, as compared to when the Off scene isactive. Other variations are possible.

Turing to the “Edit” icon 816, upon determining/detecting that a userhas selected the icon, the control application may display to the uservia a visual display of network device 680 the example configurationinterface 901 shown in FIG. 6R. Interface 901 may include a firstsection 902 related to the type indicator associated with the keypadcontrol device, for example, and that may allow the user via the controlapplication to change the type indicator (here, “Keypad”) associatedwith the keypad control device(s). Section 902 may be, for example, adrop-down menu, and/or free text field, etc. Interface 901 may alsoinclude a section 903 related to the location indicator associated withthe keypad control device, for example, and that may allow the user viathe control application to change the location indicator (here,“Kitchen”) associated with the keypad control device. According to thisexample, the keypad control device is currently indicated as beinglocated in the “Kitchen.” The word “Kitchen” may be a selectable iconthat allows the user to change the location associated with the device,although other mechanisms may be used. Upon determining/detecting that auser has selected the “Kitchen” icon 903, the control application maydisplay to the user an example interface 909 as shown in FIG. 6S. Thecontrol application may list in interface 909 a selection of possiblelocations/rooms 908 to associate with the keypad control device. Asshown, the control application may provide an indication of the locationcurrently associated with the keypad control device. In this example, a“check” mark is shown next to “Kitchen,” although other mechanisms maybe used. Any one (or possibly more) of the locations/room 908 may beselectable by the user. Upon detecting determining that the userselected a new location/room, the control application may associate a“check” mark with new location for example, possibly removing the“check” mark from the prior location (as another example, a given“checked” location may need to be selected by the user to un-select thelocation. Other variations are possible). Although not shown, interface909 may allow a user to specify a location not shown in list 908. Oncedone, the user may select either of the “Cancel” icon 907 or the “Save”icon 906. Selection of the “Cancel” icon 907 may cause the controlapplication to not save any changes made by the user via interface 909and return the user to interface 901. Selection of the “Save” icon 906may cause the control application to save any changes made by the uservia interface 909 and return the user to interface 901.

Returning to FIG. 6R, if the user changed the location associated withthe keypad device via interface 909, that location may be reflected insection 903. Interface 901 may also include a respective pane or section905 a-905 d, each corresponding to one of the scene actuators/buttons ofthe keypad device. Each pane 905 a-905 d may include a name associatedwith the respective scene (here again, “Bright,” “Cooking,” Dining,” and“Off”). The name may be a selectable icon, although mechanisms may beused. Each pane may also include a brief description of the controldevices (lights, speakers, shades) associated with the scene (i.e., anindication as to which control devices are controlled by a given scene).By selecting one of the icons in panes 905 a-905 d, a user may changethe scene assigned to the respective button of the keypad controldevice. For example, upon detecting/determining that the user selectedthe “Bright” icon to change the Bright scene, the control applicationmay display to the user the example configuration interface 910 shown inFIG. 6T. Interface 910 may include a respective icon 912 a and 912 bcorresponding to the control devices (lighting, shade, speaker, etc.)associated with the selected scene (here, two icons respective lightingcontrol devices/lighting loads are shown) and possible settings of eachdevice/load for the scene (here, each lighting load is set to 100% forthe scene). Icons 912 a and 912 b may be selectable icons that uponselection by the user, allows the user, via an interface, toindividually control, for example, the settings (e.g., dimming level,shade level, etc.) for that respective control device/load. Because theBright scene contains lighting devices, example interface 910 may alsoinclude selectable control icon 911, selection of which by the user mayallow the user to change the dimming level (up and down) of thedisplayed lighting control devices/loads 912 a and 912 b intandem/together. Any changes to the dimming levels may be reflected inicons 912 a and 912 b. Interface 915 may also include a selectable icon915 that allows the user to add and/or remove control devices associatedwith the Bright scene.

For example, upon detecting/determining that the user selected icon 915,the control application may display to the user the exampleconfiguration interface 916 shown in FIG. 6U. The control applicationmay list in interface 916 possible control devices/loads 917 in the loadcontrol system 210 a that may be controlled by the keypad and that theuser may associate/add to and/or remove from the current scene (here,the Bright scene). According to one example, control devices/loads 917that are located in the same room as the keypad may be listed first(here, Kitchen devices) followed by other control devices/loads in theload control system (here, Office Table Lamp). As show, the variouscontrol devices/loads 917 may be selectable/un-selectable by the user(selected control devices/loads 917 being designated by a “check” markfor example) to add/remove the devices from the scene. Interface 916 mayfurther allow the user to configure levels (e.g., dimming levels, shadelevels, etc.) for each selected device, such as by selecting the iconassociated with the control device and an additional interface beingshown. Interface 916 may further include control icons 918 a and 918 b aselection of which may allow a user to select all displayed controldevices, or unselect all control devices. Once done, the user may select“carrot” 920 (although other mechanisms may be used) to return tointerface 910 of FIG. 6T. Upon returning to interface 910, the interfacemay include icons 912 a/912 b reflective of choices made in interface916. Once done, the user may select either of the “Cancel” icon 913 orthe “Save” icon 914. Selection of the “Cancel” icon 913 may cause thecontrol application to not save any changes made by the user viainterface 910 and return the user to interface 901. Selection of the“Save” icon 906 may cause the control application to save changes madeby the user via interface 910 and return the user to interface 901.

Referring again to interface 901, it may also include a “Delete keypad”icon 904. Actuation of this icon may cause the control application toinstruct the system controller to remove the keypad control device fromthe load control system. Assuming the user makes changes to the keypadscenes, once done the user may select “carrot” 921 (although othermechanisms may be used) to return to either interface 812 or 610 forexample. Any changes made by the user regarding the editing of thekeypad control device may be communicated by the control application tothe system controller, which may then reconfigure the load controlsystem accordingly, including the keypad control device(s). In addition,if a keypad control device's location is changed such as throughinterface 909, the control application may move the respective icon inthe Devices tab 642 to a new pane representative of the new location,for example. Similarly, if a keypad control device is removed from theload control system, the corresponding icon may be removed from theDevices tab 642, for example.

According to a further aspect, a keypad control device may communicatewith other control devices to effectuate a scene. These other controldevices may have respective icons as discussed herein, such as inDevices tab 642, for example. The control application may change theappearance of such icons as described herein as a scene is controlledvia interface 812 or the actual keypad control device. Similarly,actuating a scene via interface 812 or an actual keypad control devicemay cause the control application to update the number valuesrepresented by the icons of section 620 for example, as a controldevice's state changes as describe herein. Other variations arepossible.

One will recognize that the interfaces of FIG. 6R-FIG. 6U are examplesand other variations are possible. For example, responsive to a userselecting the “Edit” icon 816 of control interface 812 of FIG. 6Q, thecontrol application may display to the user via a visual display ofnetwork device 680 the example configuration interface 901′ shown inFIG. 6V. Similar to interface 901 of FIG. 6R, interface 901′ may includea first section/field 902′, for example, related to the name associatedwith the keypad control device, for example, and that may be configuredto enable the user via the control application to change the name (here,“Keypad”) associated with the keypad control device. Interface 901′ mayalso include an/actuator 903′, for example related to the locationindicator associated with the keypad control device, for example, andthat may be configured to enable the user via the control application tochange the location indicator (here, “Kitchen”) associated with thekeypad control device (e.g., by providing access to a menu/drop downmenu). Interface 901′ may also include a respective panes or sections905 a′-905 d′, each corresponding to one of the scene actuators/buttonsof the keypad device. Each pane 905 a′-905 d′ may include a nameassociated with the respective scene (here again, “Bright,” “Cooking,”Dining,” and “Off”). Each pane may be selectable (such as via arespective icon or carrot 923). Interface 901′ may also include a“Delete” icon 904′, that may be similar to Delete icon 904.

Assuming the control application detects a selection of one of the icons923, a user may change the scene assigned to the respective button ofthe keypad control device. For example, upon detecting/determining thatthe user selected the icon 923 associated with the “Bright” scene, thecontrol application may display the example configuration interface 916′shown in FIG. 6W. The control application may list/display in interface916′ possible control devices/loads 917′ in the load control system 210a that may be controlled by the keypad and that the user mayassociate/add to and/or remove from the current scene (here, the Brightscene) (interface 916′ may be scrollable). According to this example,control devices/loads 917′ are separated by location (e.g., “Kitchen”,“Living Room”, “Dining Room”, etc.). As show, the various controldevices/loads 917′ may be selected/un-selected by the user (selectedcontrol devices/loads 917′ being designated by a “check” mark forexample) to add/remove, respectively, the control devices from thescene. For selected control devices that are part of a scene (here, the“Main Lights” and the “Pendants”), the control application may alsodisplay the level of the device with respect to the scene (here, bothdevices are shown to be fully “On” as part of the Bright scene (similarindicators may be shown for other control devices/loads such as shades).For selected control devices that are part of a scene (here, the “MainLights” and the “Pendants”), interface 916′ may also include arespective icon or carrot 919, for example, to configure the level ofthe device. For example, in response to the control applicationdetecting that a user has selected icon 917 associated with the “MainLights,” the control application may expand interface 916′ to display acontrol interface 922 as shown in the example of FIG. 6X. Here, controlinterface 922 is shown with a vertically movable/slide-able actuator 922a that may be actuated/slid by the user to change the light level, andalso includes a set of buttons/actuators 922 b (here four—one to set thelevel to fully on, one to raise the level, one to lower the level, andone to set the level to off, for example) that may be actuator to setthe level (other variations are possible). The control application maydisplay the actuator 922 a, for example, to provide an indication to theuser of the respective device's current setting (here, fully On).Responsive to a user selecting the actuators 922 a and/or 922 b, thecontrol application may change the displayed level setting from “On” toa value representative of the new level as set by the user. Upondetecting a further selection of icon 919 associated with the “MainLights”, the control application may collapse interface 916′ as shown inFIG. 6W.

Interface 916′ may also include example selectable icons/actuators 918a′, 918 b′, and 918 c′ (although fewer and/or additional icons may beshown). These icons may allow a user to more easily display controldevices of interest in interface 916′. For example, icon 918 a′ may betoggled between selected and unselected. When selected, the controlapplication may display “All” control devices, for example, within theload control system. Unselecting icon 918 a′, may cause the controlapplication to display no control devices. Icon 918 b′ may also betoggled between selected and unselected. When icon 918 b′ is selected,the control application may deactivate selection of icon 918 a′ (ifselected) for example, and only display in interface 916′ the lightingcontrol devices that are part of the load control system. When icon 918b′ is unselected, the control application may remove from interface 916′the lighting control devices. Similarly, icon 918 c′ may be toggledbetween selected and unselected. When icon 918 c′ is selected, thecontrol application may deactivate selection of icon 918 a′ (ifselected) for example, and only display in interface 916′ the shadedevices that are part of the load control system. When icon 918 c′ isunselected, the control application may remove from interface 916′ theshade devices. One will recognize that both icon 918 b′ and 918 c′ maybe selected such that both lighting control devices and shade devicesare displayed. One will recognize that other variations are possible. Auser may or may not save changes made via interface 916′ as similarlydiscussed above. Any changes made by the user regarding the editing ofthe keypad control device may be communicated by the control applicationto the system controller, which may then reconfigure the load controlsystem accordingly. Similarly, changes may be reflected in otherinterfaces as discussed herein.

The interfaces of FIGS. 6Q-6X may be applicable to various types ofkeypads, including handheld remote keypads that control scenes.

Overall, the Devices tab 642 allows a user to easily determine thecontrol devices within different locations of the user environment, todetermine the status of the control devices, and to easily control thedevices.

Turning now to FIG. 6Y, upon determining/detecting that a user hasselected Scenes tab 644, the control application may display an exampleinterface 820. Interface 820 may be similar to interface 610, continuingto display section 620 and respective status information, and with theScenes tab now shown as active (e.g., as shown by the under-bar 822,although other means may be used such as reverse highlighting, etc.).When the Scenes tab is selected, the control application may configuresection 660 to display information presenting one or more scenes thatmay be activated by the user. Specifically, as indicated above thesystem controller 250 a may maintain information related to one or morepre-programmed scenes that may be actuated by a user from the controlapplication. Each scene may include a scene name, certain settings(e.g., dimming levels) for one or more lights, certain setting for oneor more shades, etc. Other examples are possible. The controlapplication may obtain information on each scene from the systemcontroller 250 a and display respective information on these scenes tothe user in information section 660.

As shown in FIG. 6Y, the control application may subdivide section 660into multiple panes (here three panes are shown, 824, 826, and 828).Each pane may represent and/or contain information on each scenemaintained by the system controller. For example, within each pane 824,826, and 828 the control application may display a selectable icon (suchas icons 830 a-c) representative of the scene and may further displayinformation (such as textual information like “Wake,” “Entertain,” and“Basement Off”) that may provide a description of the scene. Again,different icons may be used for different scenes and the systemcontroller may provide the control application with an indication ofwhich icon to display, for example. If there are more scenes than canfit in section 660, the section may be vertically scrollable, forexample, to display additional scenes, similar to the description ofFIGS. 6O and 6P as described above.

According to a further aspect of the Scenes tab 644, the controlapplication may display the icons 830 a-830 c in section 660 in afashion to provide an indication of the status/state of the scene, i.e.,whether the scene is activated or is not activated. For example, thecontrol application may change the appearance of the icon (e.g., changeits color and/or contrast as compared to other icons) to signify thestatus/state of the corresponding scene.

Upon determining/detecting that a user has selected a given icon 830a-830 c, the control application may communicate one or more messages tothe system controller indicating the scene was selected or unselected(to either activate or deactivate the scene). The system controller mayin turn configure respective control devices according to the scenebeing activated or deactivated (e.g., turned on or off). As deviceschange states due to changing scenes, the control application may updatesection 620 accordingly.

As further shown in FIG. 6Y, each scene may also include a selectable“pencil” icon 832 a-832 c, for example, that when selected may cause thecontrol application to display to the user an interface that will allowthe user to reconfigure the scene. Reconfiguring a scene may includeadding and/or removing one or more control devices from the scene,altering settings (such as dimming levels) of one or more controldevices that are part of the scene, deleting a scene, etc. Thereafter,the control application may communicate the changes via one or moremessages to the system controller.

As also shown in FIG. 6Y, section 660 may include an “Add scene” icon834, for example, that when selected by a user, may cause the controlapplication to display to the user an interface that will allow the userto create a new scene. Creation of a new scene may cause the controlapplication to communicate one or more messages to the system controllerindicating/defining the new scene and may further cause the controlapplication to add the scene to section 660 such that the user mayactivate the scene. One will recognize that other variations arepossible.

Turning now to FIG. 6Z, upon determining/detecting that a user hasselected Schedules tab 646, the control application may display anexample interface 840 to the user. Interface 840 may be similar tointerface 610, continuing to display section 620 and respective statusinformation, and with the Schedules tab now shown as active (e.g., asshown by the under-bar 848, although other means may be used such asreverse highlighting, etc.). When the Schedules tab is selected, thecontrol application may configure section 660 to display informationcorresponding to one or more timeclock schedules that the systemcontroller is configured to perform. Specifically, as indicated abovethe system controller 250 a may maintain information related to one ormore pre-programmed timeclock schedules that the system controller mayautomatically perform. Each schedule may include a schedule name,certain settings (e.g., dimming levels) for one or more lights, certainsetting for one or more shades, and times/dates as to when the systemcontroller should activate/deactivate the schedule, etc. Other examplesare possible. The control application may obtain information on eachschedule from the system controller and display respective informationon these schedules to the user in information section 660.

As shown in FIG. 6Z, the control application may subdivide section 660into multiple panes (here three panes are shown, 842, 844, and 846).Each pane may represent and/or contain information on each schedulemaintained by the system controller. For example, within each pane 842,844, and 846 the control application may display information (such astextual information like “Front Porch Lights,” “Holiday Lights,” and“Shades Open/Close”) that may provide a description of the schedule. Theinformation may further include a description of when the respectiveschedule is to be activated. If there are more schedules than can fit insection 660, the section may be vertically scrollable, for example, todisplay additional schedules similar to the description of FIGS. 6O and6P as described above

As further shown in FIG. 6Z, each schedule may also include a selectable“pencil” icon 852 a-852 c, for example, that when selected, may causethe control application to display to the user an interface that mayallow the user to reconfigure the schedule. Reconfiguring a schedule mayinclude adding and/or removing one or more control devices from theschedule, altering settings (such as dimming levels) of one or morecontrol devices that are part of the schedule, deleting a schedule,changing timing of the schedule, etc. Thereafter, the controlapplication may communicate the changes via one or more messages to thesystem controller for implementation. Other variations are possible.

For example, referring to FIG. 6AA there is shown another exampleinterface 840′ with the Schedules tab active. Interface 840′ may besimilar to interface 840, with section 660 subdivided into one morepanes (here three panes are shown, 842′, 844′, and 846′). Each pane mayrepresent and/or contain information on each schedule maintained by thesystem controller. For example, within each pane 842′, 844′, and 846′the control application may display information (such as textualinformation like “Porch Lights On,” “Porch Lights Off,” and “Wake”) thatmay provide a description of the schedule. The information may furtherinclude a description of when the respective schedule is to be activatedwith respective to days of the week (for example, the “Wake” schedule isscheduled for weekdays only). According to this example, the controlapplication may also display for each schedule a respective icon 953 a,953 b, and 953 c. The control application may display in connection witheach icon/schedule (such as inside the icon) the time as to when theschedule is to activate/start running. According to this example, a usermay configure a schedule to activate relative to astronomical time(e.g., relative to sunrise and sunset) or relative to a set clock time(e.g., 9:00 AM). In this example, the “Porch Lights On” and “PorchLights Off” schedules are astronomical schedules configured to activaterelative to sunset and sunrise, respectively. As a result, theseschedules may start at different clock times each day as the yearprogresses since sunset and sunrise may change day to day. In thisexample, the “Wake” schedule is relative to clock time and starts thesame static time each weekday at 6:30 am. As further shown in FIG. 6AA,each schedule may also include a selectable “pencil” icon 852 a′-852 c′,for example, that when selected, may cause the control application todisplay to the user an interface that may allow the user to reconfigurethe schedule.

According to one example, the control application may display schedulesin section 660 in order of time as the schedules are set toactivate/start running. Hence, the current schedule or next toactivate/run schedule (if there is no current schedule) may be shownfirst (e.g., at the top of section 660), followed by the next scheduleto activate, etc. As a schedule completes (ends), the controlapplication may remove the schedule from the top of the list and shiftup the other schedules, possibly moving the removed schedule to thebottom of the list (other orderings are possible). Because someschedules may be relative to astronomical time, the control applicationmay change the ordering of the displayed schedules from day to daythroughout the year since these schedules do not start at the samestatic set time each day.

According to a further aspect of interface 840′, the control applicationmay display to the user the state of a given schedule, where there maybe one or more possible states. As one example, there may be threestates including (i) a deactivated state, where the schedule is not setto activate/run at its designated time (e.g., a schedule may bedeactivated because the user deactivated the schedule, or because theschedule is not set to activate on the current/present day of the week,etc.), (ii) an activated-match state, where the schedule is set toactivate or is currently activated at its designated time and allcontrol devices that are part of the schedule are currently in a statethat matches the schedule, and (iii) an activated-un-match state, wherethe schedule is set to activate or is currently activated at itsdesignated time but all control devices that are part of the scheduleare currently not in a state that matches the schedule. One willrecognize that fewer or additional states are possible. According to oneexample, the control application may use icons 953 a-953 c to indicateto the user the state of each schedule, such as by changing the icon,changing the appearance of the icon such as through color or reversehighlighting, etc. In this example, assuming it's a Saturday at 3 PM,the sun is out, and the porch lights are off, the “Porch Lights On”schedule may be shown first/at the top of section 660 as being the nextto activate, followed second by the “Porch Lights Off” schedule, andthird by the “Wake” schedule. The control application may show the icon953 a of the “Porch Lights On” schedule as the schedule being in theactivated-un-match state because the scheduled is set to activate atsunset but the porch lights are off and thus do not currently match theconfiguration of the schedule (the state of this schedule may change tothe activated-match state once the porch lights are on). The controlapplication may show the icon 953 b of the “Porch Lights Off” scheduleas the schedule being in the activated-match state because the scheduleis set to activate at sunrise and the porch lights, currently being off,matches the configuration of the schedule. The control application mayshow the icon 953 c of the “Wake” schedule as the schedule being in thedeactivated state in that the schedule is not configured to run onweekends, for example. This is one example, and other examples arepossible.

As also shown in FIG. 6Z and FIG. 6AA, section 660 may include an “Addevent” icon 850 or “Add schedule” icon 850′ for example that whenselected, may cause the control application to display to the user aninterface that will allow the user to create a new schedule. Creation ofa new schedule may cause the control application to communicate one ormore messages to the system controller indicating/defining the newschedule and may further cause the control application to add theschedule to section 660.

One will recognize that sections/panes 620, 640, and 660 of thegraphical interfaces shown in FIGS. 6A, 6O, 6Y, and 6Z for example, maybe shown in different orders. For example, the graphical interfacesdescribe herein have section 620 vertically positioned over section 640,and section 640 vertically positioned over section 660 when displayed ona visual display of a network device 680. As another example, section640 may be vertically positioned over section 660, and section 660 maybe vertically positioned over section 620 when the sections aredisplayed on a visual display of a network device 680. Other orders arepossible. As another example, section 620 may be a vertically orientedpane/section compared to a horizontally oriented pane (i.e., the iconsmay be positioned vertically, rather than horizontally). Here, pane 620may be position to the left or right of panes 620 and 640 for example.

Nonetheless, as discussed herein, status section 620 may provide a userwith an aggregated summary of the load control system 210 a, and therespective icons may provide a user with access to control devices theuser may more likely want to control as compared to other devices.Hence, having section 620 positioned over sections 640 and 660 (i.e., atthe top of a visual display of a network device 680) may make thissection more easily accessible to the user.

One will recognize that in addition to the above description, otherexamples are possible. For example, referring to FIG. 7A, there is shownanother example graphical user interface 1510 that may be initiallydisplayed by the control application to a user via network device 680upon the application initially starting. Interface 1510 may be similarto interface 610 as shown in FIG. 6A, for example, and may include threesections or panes including a status section 620, a menu selectionsection/tab section 640, and in information section 660. According tothis example and as similarly discussed above, section 620 of interface1510 may include one or more icons indicating different statusinformation of one or more control devices 220 a within the load controlsystem 210 a. Here, a lighting devices icon 1522, shades devices icon1524, and a thermostat devices icon 1526 are shown, although asdiscussed above, additional and/or other and/or fewer icons may be shownsuch as an audio devices icon and/or a fan devices icon depending on thecontrol devices 220 a within the load control system 210 a. Section 620may be configured to be scrollable by the user (such as left to right orup/down) in order to display additional icons and/or may be configuredsuch that there are multiple rows of icons displayed at one time to auser, again depending on the control devices 220 a within the loadcontrol system 210 a. According to this example, the status ofrespective devices may be shown by the control application to a user viaa numerical value and/or text associated with the icon and inparticular, may be shown below the icon (here, “10 On”, “3 Open”,“Currently”), as compared to a number, for example, imposed on the iconas shown in FIG. 6A. As another example, lighting devices (and similarlyfan devices) in an “off” state may have the status shown as “0 On” or“All Off”. Shade devices in a closed state may have the status shown as“0 Open” or “All Closed”, for example. Again, other variations arepossible including the format used in FIG. 6A for example. The iconsshown in section 620 may be selectable by a user as discussed above,with the control application taking the user to subsequent userinterfaces (such as interface 702 of FIG. 6C in response to selection oficon 1522). Similarly, the status information associated with each iconmay be dynamically/actively updated by the control application as thestatus of control devices change.

As similarly discussed above with reference to FIGS. 6O, 6Y, and 6Z forexample, section 660 of interface 1510 may be vertically scrollable, forexample, when any of the Devices tab 642, Scenes tab 644, Schedules tab646 is active. Using the Devices tab 642 as the active tab as anexample, as section 660 is scrolled “downward” (and/or as panes areexpanded) to reveal additional pane information, such as additionalinformation of “Master Bedroom” pane 1586 and/or additional panes below“Master Bedroom” pane 1586, section 660 may expand, with section 620scrolling off of and/or disappearing from and/or being removed from thedisplay interface of the network device and section 660 consuming thisspace. Alternatively and as shown in FIG. 7B, section 620 may becondense or be minimized by the control application as section 660expands. For example, as shown in FIG. 7B, the icons, such as icons1522, 1524, and 1526, may be removed by the control application but thenumerical and/or text based status information, for example, may becontinued to be displayed for one or more types of devices to providestatus information to a user (here, “10 Lights On” for lighting devices,“3 Shades Open” for shade devices, and “Currently 72°” for thermostatdevices). The displayed information and format are an example and otherexamples are possible. Condensed/minimized section 620 of interface 1510may be configured to be scrollable by the user (such as left to right orup/down) in order to display additional status information and/or may beconfigured such that there are multiple rows of information displayed atone time to a user. Alternatively, condensed/minimized section 620 ofinterface 1510 may not be scrollable and may only display statusinformation for a subset of control devices. Which devices are displayedmay or may not be user definable. The status information shown incondensed/minimized section 620 of interface 1510 may bedynamically/actively updated by the control application as the status ofcontrol devices change. According to one example, condensed/minimizedsection 620 of interface 1510 may be configured to allow a user toselect various portions (such as “10 Lights On”, “3 Shades Open”, and“Currently 72°”) with the control application taking the user tosubsequent user interfaces as discussed above. According to anotherexample, condensed/minimized section 620 of interface 1510 may beconfigured such that in response to a user selecting section 620, thesection may be re-expanded and section 660 may be collapsed by thecontrol application, returning to the configuration as shown in FIG. 7A.Thereafter, section 620 may be configured to allow a user to selectdisplayed icons as discussed above. Continuing to refer to FIG. 7B,continued “downward” scrolling of section 660 may cause the panes at thetop of the section (here “Kitchen” pane 1582) to disappear from section660 and for additional panes to appear at the bottom (below “MasterBedroom” pane 1586) of the section 660, assuming there are additionalpanes. Similarly, as section 660 is scrolled “upward” in the reversedirection (to possibly reveal panes such as pane 1582 that may have beenscrolled off of section 660), panes at the bottom of section 660 maydisappear from section 660 (such as pane 1586) and additional panes mayappear at the top of section 660. Continued “upward” scrolling (and/orcollapsing of panes of section 660) may cause section 660 to collapse asthe top pane (here “Kitchen” pane 1582) is reached, and for section 620to re-expand, with interface 1510 once again appearing as shown in FIG.7A. According to another example, in addition to and/or as analternative to the above, selecting the Devices tab 642 (such as by“touching” or “tapping”) in the FIG. 7A configuration may cause section660 to expand and section 620 to collapse as shown in FIG. 7B. Again,section 660 may then be scrollable. Similarly, selecting the Devices tab642 and/or section 620 (such as by “touching” or “tapping”) in the FIG.7B configuration may cause section 660 to collapse and section 620 to bere-expand as shown in FIG. 7A. Hence, the expanding and collapsing ofsections 620 and 660 may be achieved/obtained in various ways includingthrough scrolling actions and/or by selecting section 620 and/or theDevices tab 642. Again, the Scenes tab 644 and the Schedules tab 646 mayoperate in a similar fashion.

Referring now to FIG. 8A, there is shown another example graphical userinterface 1610 that may be initially displayed by the controlapplication to a user via network device 680 upon the applicationinitially starting. Interface 1610 may be similar to interface 1510 asshown in FIG. 7A, for example, and may include three sections or panesincluding a status section 620, a menu selection section/tab section640, and in information section 660. According to this example and assimilarly discussed above, section 620 of interface 1610 may include oneor more icons indicating different status information of one or morecontrol devices 220 a within the load control system 210 a. Here, alighting devices icon 1622, shades devices icon 1624, and a thermostatdevices icon 1626 are shown. According to this example, the status iconsare now arranged vertically, rather than horizontally. As further shownin FIG. 8A, the status of respective devices may be shown to a user viaa numerical value and/or text associated with the icon and inparticular, may be shown below the icon (here, “8 Lights On”, “3 ShadesOpen”, “Currently”), as compared to a number, for example, imposed onthe icon as shown in FIG. 6A. Nonetheless, one will recognize the formatused in FIG. 6A may also be used in interface 1610. Similarly, othervariations are possible. As a further example, lighting devices (andsimilarly fan devices) in an “off” state may have the status shown as “0Lights On” or “All Lights Off”. Shade devices in a closed state may havethe status shown as “0 Shades Open” or “All Shades Closed”, for example.The icons shown in section or pane 620 may be selectable by a user asdiscussed above, with the control application taking the user tosubsequent user interfaces (such as interface 702 of FIG. 6C in responseto selection of icon 1622). Similarly, the status information associatedwith each icon may be dynamically/actively updated by the controlapplication as the status of control devices change.

According to the example show in FIG. 8A, the load control system 210 aincludes three types of devices including lighting control devices,shade devices, and thermostat devices. Accordingly, the interface 1610shows three corresponding icons in section 620. As discussed herein, aload control system may include fewer, other, and/or additional controldevices, with section 620 thus including fewer, other, and/or additionalicons. According to an aspect of interface 1610, the default sizeconfiguration of section 620 and section 660 may be based on the numberof icons (i.e., types of control devices of the load control system)within section 620. For example, as the load control system includes anincreasingly larger number of control device types, the default size ofsection 620 may be increased in size by the control application todisplay additional icons and the default size of section 660 may bedecreased in size. Similarly, as the load control system includes adecreasingly smaller number of control device types, the default size ofsection 620 may be decreased in size by the control application todisplay fewer icons and the default size of section 660 may be increasedin size. For example, as shown in the example of FIG. 8A, section 660shows two panes 1682 and 1684 of the active Devices tab 642 (similarly,if the Scenes tab 644 or Schedules tab 646 were active, section 660 maydisplay information relative to these tabs). As another example,assuming the load control system 210 a includes fewer control devicetypes, section 620 may include fewer icons and respective statusinformation. For example, referring to FIG. 8B, assuming the loadcontrol system 210 a only includes lighting control devices, section 620may only include icon 1622 and corresponding status information.According to this example, section 660 now consumes additional remainingspace of interface 1610 as compared to FIG. 8A, here showing six panes,1682, 1684, 1686, 1688, 1690, and 1692 (similarly, if the Scenes tab 644or Schedules tab 646 were active, section 660 may display informationrelative to these tabs). According to another example and as shown inFIG. 8C, assuming the load control system 210 a includes not onlylighting control devices, shade devices, and thermostat devices but alsoincludes audio and fan devices, section 620 may now include five icons1622, 1624, 1626, 1628, and 1630 respectively, and associated statusinformation. According to this example, section 660 is no longerdisplayed in interface 1610. According to this example, section 620 maybe vertically scrollable to display additional icons if the load controlsystem includes still additional load control types. One will recognizethat FIGS. 8A, 8B, and 8C are examples and other variations arepossible. For example, with respect to FIG. 8C, more than five icons maybe displayed at one time in section 620. Similarly, fewer than fiveicons may be displayed in section 620, with section 620 still consumingthe space of the interface 1610 and section 660 not being shown.

Referring again to the example of FIG. 8A (the example of FIG. 8B mayoperate in a similar fashion), as similarly discussed above withreference to FIGS. 7A and 7B, section 660 of interface 1610 may bevertically scrollable, for example, when any of the Devices tab 642,Scenes tab 644, Schedules tab 646 is active. Using the Devices tab 642as the active tab as an example, as section 660 is scrolled “downward”(and/or as panes are expanded) to reveal additional pane information,such as additional panes below “Living Room” pane 1684, section 660 mayexpand, with section 620 scrolling off of and/or disappearing fromand/or being removed from the display interface of the network device bythe control application and section 660 consuming this space.Alternatively and as shown in FIG. 8D, section 620 may condense or beminimized by the control application as section 660 expands. Forexample, as shown in FIG. 8D, the icons, such as icons 1622, 1624, and1626, may be removed but the numerical and/or text based statusinformation or a variation thereof, for example, may be continued to bedisplayed by the control application for one or more types of devices toprovide status information to a user (here, “10 Lights On” for lightingdevices, “3 Shades Open” for shade devices, and “Currently 72°” forthermostat devices). The displayed information and format are an exampleand other examples are possible. Condensed/minimized section 620 ofinterface 1610 may be configured to be scrollable by the user (such asleft to right or up/down) in order to display additional statusinformation and/or may be configured such that there are multiple rowsof information displayed at one time to a user. Alternatively,condensed/minimized section 620 of interface 1610 may not be scrollableand may only display status information for a subset of control devices.Which devices are displayed may or may not be user definable. The statusinformation shown in condensed/minimized section 620 of interface 1610may be dynamically/actively updated by the control application as thestatus of devices change. According to one example, condensed/minimizedsection 620 of interface 1610 may be configured to allow a user toselect various portions (such as “10 Lights On”, “3 Shades Open”, and“Currently 72°”) taking the user to subsequent user interfaces asdiscussed above. According to another example, condensed/minimizedsection 620 of interface 1610 may be configured such that in response toa user selecting section 620, the section may be re-expanded and section660 may collapsed by the control application, returning to theconfiguration as shown in FIG. 8A, for example. Thereafter, section 620may be configured to allow a user to select displayed icons as discussedabove. Continuing to refer to FIG. 8D, continued “downward” scrolling ofsection 660 may cause the panes at the top of the section (here“Kitchen” pane 1682) to disappear from section 660 and for additionalpanes to appear at the bottom (below “Master Bedroom” pane 1686) of thesection 660, assuming there are additional panes. Similarly, as section660 is scrolled “upward” in the reverse direction (to possibly revealpanes such as pane 1682 that may have been scrolled off of section 660),panes at the bottom of section 660 may disappear from section 660 (suchas pane 1686) and additional panes may appear at the top of section 660.Continued “upward” scrolling (and/or collapsing of panes of section 660)may cause section 660 to be collapsed by the control application as thetop pane (here “Kitchen” pane 1682) is reached, and for section 620 tore-expand, with interface 1610 once again appearing as shown in FIG. 8A,for example. According to another example, in addition to and/or as analternative to the above, selecting the Devices tab 642 (such as by“touching” or “tapping”) in the FIG. 8A (and similarly FIG. 8B)configuration may cause section 660 to be expanded and section 620 to becollapsed by the control application as shown in FIG. 8D. Again, section660 may then be scrollable. Similarly, selecting the Devices tab 642and/or section 620 (such as by “touching” or “tapping”) in the FIG. 8Dconfiguration may cause section 660 to collapse and section 620 tore-expand as shown in the FIG. 8A (and similarly FIG. 8B) configuration.Hence, the expanding and collapsing of sections 620 and 660 may beachieved/obtained in various ways including through scrolling actionsand/or by selecting section 620 and/or the Devices tab 642. Again, theScenes tab 644 and the Schedules tab 646 may operate in a similarfashion.

Referring again to FIG. 8C and sections 662 and 660, this configuration(where section 660 is not initially shown) may operate similar to thatdescribed above for FIG. 8A. Using the Devices tab 642 as the active tabas an example, a selecting of the interface 1610 in an area belowsection 640 (i.e., where section 660 may be) for example, and “swiping”upward for example (although other mechanism may be used) may causesection 660 to appear, with section 620 scrolling off of and/ordisappearing from and/or being removed from the display interface of thenetwork device by the control application and section 660 consuming thisspace. Alternatively and as shown in FIG. 8D and as discussed above,section 620 may condense or be minimized as section 660 appears. Theconfiguration of FIG. 8D may then operate as described above. Forexample, condensed/minimized section 620 of interface 1610 may beconfigured to be scrollable by the user (such as left to right orup/down) in order to display additional status information and/or may beconfigured such that there are multiple rows of information displayed atone time to a user. Alternatively, condensed/minimized section 620 ofinterface 1610 may not be scrollable and may only display statusinformation for a subset of control devices. Which devices are displayedmay or may not be user definable. The status information shown incondensed/minimized section 620 of interface 1610 may bedynamically/actively updated by the control application as the status ofdevices change. According to one example, condensed/minimized section620 of interface 1610 may be configured to allow a user to selectvarious portions (such as “10 Lights On”, “3 Shades Open”, and“Currently 72°”) with the control application taking the user tosubsequent user interfaces as discussed above. According to anotherexample, condensed/minimized section 620 of interface 1610 may beconfigured such that in response to a user selecting section 620, thesection may re-expand and section 660 may scroll off of and/or disappearfrom and/or be removed from the display interface, returning to theconfiguration as shown in FIG. 8D, for example. Thereafter, section 620may be configured to allow a user to select displayed icons as discussedabove. Continuing to refer to FIG. 8D, section 660 may be upward anddownward scrollable as discussed above. Similarly, continued “upward”scrolling (and/or collapsing of panes of section 660) may cause section660 to scroll off of and/or disappear from and/or be removed from thedisplay interface as the top pane (here “Kitchen” pane 1682) is reached,and for section 620 to re-expand, with interface 1610 once againappearing as shown in FIG. 8D, for example. According to anotherexample, in addition to and/or as an alternative to the above, selectingthe Devices tab 642 (such as by “touching” or “tapping”) in the FIG. 8Cconfiguration may cause section 660 to expand and section 620 tocollapse as shown in FIG. 8D. Again, section 660 may then be scrollable.Similarly, selecting the Devices tab 642 and/or section 620 (such as by“touching” or “tapping”) in the FIG. 8D configuration may cause section660 to scroll off of and/or disappear from and/or be removed from thedisplay interface, and for section 620 to re-expand as shown in the FIG.8C configuration. Hence, the expanding and collapsing of sections 620and 660 may be achieved/obtained in various ways including throughscrolling and/or swiping actions and/or by selecting section 620 and/orthe Devices tab 642. Again, the Scenes tab 644 and the Schedules tab 646may operate in a similar fashion.

Again, as discussed herein, status section 620 may provide a user withan aggregated summary of the load control system 210 a, and therespective icons may provide a user with access to control devices theuser may more likely want to control as compared to other devices.

Referring now to FIG. 9A, there is shown another example graphical userinterface 1710 that may be displayed by the control application to auser via network device 680. Interface 1710 may be similar to, and mayoperate similarly to, interface 1610 as shown in FIGS. 8A-8D, forexample, and the other interfaces discussed herein. Interface 1710includes another example of how the control application may indicateoccupancy to a user of the control application. One will recognize thatthe displaying and operation of occupancy as discussed with respect toFIG. 9A (and similarly FIGS. 9B-9G) may be similarly applied to theother graphical user interfaces discussed herein.

For the purpose of describing FIGS. 9A-9G, it will be assumed that theuser environment 202 a of load control system 210 a includes four roomsincluding a “Kitchen,” a “Living Room,” a “Master Bedroom,” and a“1^(st) Floor Bathroom,” as shown in section 660 of interface 1710 ofFIG. 9A. It will be further assumed that load control system 210 aincludes for each room at least one or more lighting controldevices/lights, and further includes at least one occupancy sensorlocated in the “Living Room,” at least one occupancy sensor located inthe “Master Bedroom,” and at least one occupancy sensor located in the“1^(st) Floor Bathroom.” Each of these rooms of the load control system202 a may include other control devices. According to this example, loadcontrol system 210 a may be configured such that one or more of thelighting control devices/lights, for example, in each room may beresponsive to occupancy and/or vacancy signals generated by therespective occupancy sensor(s) located in that room (although othercontrol devices may also be responsive to occupancy and/or vacancysignals). The occupancy sensors may be standalone devices or may beintegrated with/part of lighting control devices (or other controldevices) for example. According to the example of FIG. 9A, as anoccupancy sensor detects an occupancy event/condition in a room, thecontrol application may receive from the system controller 250 a anindication of the occupancy event and display an indication/indicator(e.g., an icon) of this event to the user via interface 1710. In thisfashion, if a user is notified via interface 1710 that one or morelighting control devices (or other control devices), for example, in aroom has its respective lighting load(s) in an on state, the user mayfurther see that the room is occupied and may therefor decide not toturn off or change (e.g., dim) the lighting load(s) in that room via thecontrol application (or, for example, alter other control devices).According to a further aspect of this example, as an occupancy sensordetects a vacancy event/condition, the control application may receivefrom the system controllers 250 a an indication of the vacancy event andmay remove from the graphical user interface 1710 theindication/indicator of occupancy. According to a further aspect of theexample of FIG. 9A, as the control application initially starts, it mayreceive from the system controller 250 a the state of the occupancysensors (e.g., occupied/un-occupied) and display occupancy indicatorsaccordingly. The phrases vacancy/vacant and un-occupied may be usedinterchangeably herein. While the example of FIG. 9A-9G is describedwith respect to the occupancy sensors controlling lighting controldevices, these examples may also be applicable to the occupancy sensorscontrolling other types of control devices such as fan, shade,thermostat, and audio control devices a noted above.

Turning now more closely to FIG. 9A, graphical user interface 1710 mayinclude three sections or panes including a status section 620, a menuselection section/tab section 640, and in information section 660 assimilarly discussed herein. According to this example and as similarlydiscussed above, section 620 of interface 1710 may include one or moreicons indicating different status information of one or more controldevices 220 a within the load control system 210 a. Here, a lightingdevices icon 1722 is shown, although other or additional icons may beshown as discussed herein. According to this example, lighting devicesicon 1722 indicates that six (6) lighting control devices within theload control system have respective lighting loads currently on. Assimilarly discussed above and as discussed below, lighting devices icon1722 may be selectable by a user, taking the user to subsequent userinterface(s). Similarly, the status information (e.g., “6 Lights On”)associated with lighting devices icon 1722 may be dynamically/activelyupdated by the control application as the status of lighting controldevices changes within the load control system.

As shown in FIG. 9A, the Devices tab 642 is active (as shown by theunder-bar 643) with section 660 thereby being subdivided into four panes1782, 1784, 1786, and 1788, each representing a location within the userenvironment 202 a (here, one for each of the “Kitchen,” the “LivingRoom,” the “Master Bedroom,” and the “1^(st) Floor Bathroom”). In thisexample, each of panes 1782, 1784, 1786, and 1788 is shown as beingcollapsed and may be expanded as a result of the control applicationdetecting that a user has activated/selected a respective carrot 808. Inparticular, upon detecting/determining that a user hasactivated/selected a carrot 808, the control application may expand therespective pane to display one or more icons representing controldevices in the respective location as discussed herein. According tothis example, as a result of an occupancy sensor in a given roomdetecting an occupancy event, the control application may receive fromthe system controller 250 a an indication of the occupancy event anddisplay an occupancy indicator 1724 a, 1724 b (e.g., an icon, hererepresenting a person although other icons may be used) of thiscondition to the user within a respective pane of section 660. In thisexample, the occupancy sensor in the Living Room has detected anoccupancy event and as a result, the control application displays anoccupancy indicator 1724 a in the Living Room pane 1784 to show the roomis occupied. Similarly, the occupancy sensor in the 1^(st) FloorBathroom has detected an occupancy event and as a result, the controlapplication displays an indicator 1724 b in the 1^(st) Floor Bathroompane 1788 to show the room is occupied. In this example, the occupancysensor in the Master Bedroom has not detected an occupancy event (e.g.,is detecting a vacancy condition/is in a vacancy state) and as a result,the control application displays no occupancy indicator in the MasterBedroom pane 1786 to show the room is vacant. In this example, theKitchen does not include an occupancy sensor and as result, no occupancyindicator is shown in the Kitchen pane 1782 regardless of whether theKitchen is occupied. As the control application is initially started, itmay show the occupancy/vacancy condition of each room based on statusinformation received from the system controller 250 a. As theoccupancy/vacancy condition within a given room changes, the controlapplication may receive from the system controller an indication of thischange and update section 660 to either show or remove a respectiveoccupancy indicator 1724 a, 1724 b as appropriate.

One will recognize that this is one example. Icons other than the“person” icon 1724 a, 1724 b shown in FIG. 9A may be used to showoccupancy. Similarly, the occupancy indicator 1724 a, 1724 b may beplaced at a position other than the right corner of a pain. Similarly,occupancy indicators other than an icon may be used to show occupancy.For example, the occupancy indicator may include the control applicationchanging the background color and/or fonts used with respect to pain1784 or 1788 to show occupancy. Similarly, rather than providing anindicator to show occupancy and providing no indicator to show vacancy,an indicator may be used to show vacancy (e.g., a vacancy indicator,which may be an icon, for example) and no indicator may be provided toshow occupancy. As another example, one indicator may be used to showoccupancy (occupancy indicator) and another different indicator may beused to show vacancy (vacancy indicator), etc. Furthermore, for roomssuch as the Kitchen that may not have an occupancy sensor, the controlapplication may display in the respective pain (here pain 1782) anindicator (e.g., an icon) showing that the room has no sensor so that auser, in response to not seeing an occupancy indicator such as indicator1724 a, 1724 b, does not assume the room is vacant. Other examples arepossible.

As indicated above, upon detecting/determining that the user hasactivated/selected a carrot/icon 808, the control application may expandthe pane to display icon(s) representing control devices in thecorresponding room. For example, turning to FIG. 9B, there is shown anexample of the Living Room pain 1784 expanded as a result of the controlapplication detecting an actuation of carrot 808 of the pain, forexample. In this example, two icons 1732 a, 1732 b are shownrepresenting two lighting control devices as similarly described above.The two icons are shown in this example to indicate that one or morelighting loads corresponding to the respective lighting control devicesare on. As further shown in this example, pain 1784 also includes anicon 1732 c representing the occupancy sensor located in the LivingRoom. The control application may further associate with icon 1732 c anindication or label (here “Occupancy Sensor”) to provide furtherinformation about the sensor. As another example, the label may provideinformation such as where the sensor is located in the room, whichlighting control devices the sensor controls, etc. Such information maybe maintained by the system controller 250 a and provided to the controlapplication for display. As discussed below, a user may be able tochange this label from the control application. One will recognize thaticons other than icon 1732 c may be used to represent the occupancysensor. Each of icons 1732 a, 1732 b may be selectable as discussedabove to allow a user to control/configure the respective lightingcontrol device. Similarly, icon 1732 c may be selectable to allow a userto control/configure and/or test the occupancy sensor(s) and/or thelighting control devices the sensor(s) is configured to control. Asshown in this example, the control application may continue to displaythe occupancy indicator 1724 a when the pain is expanded to show theroom is occupied. As the occupancy/vacancy condition within the LivingRoom changes, the control application may receive from the systemcontroller 250 a an indication of this change and update pane 1784 toeither show or remove the occupancy indicator 1724 a, as appropriate.Similar to icons 1732 a, 1732 b for the lighting control devices, thecontrol application may change the appearance of icon 1732 c (e.g.,change its color and/or contrast) to signify a status/state of thesensor. For example, the icon may be shown in one color/contrast torepresent that the sensor is detecting an occupied condition/state andanother color/contrast to represent that the sensor is detecting avacancy condition/state. One will recognize that pain 1784 may includemultiple sensor icons if the room has multiple occupancy sensors.According to one example, the load control system may be configured suchthat the sensors are configured differently and/or different controldevices are responsive to each sensor. According to another example, agiven room may include multiple occupancy sensors that are configuredthe same (such as if the room is large, has an irregular shape, etc.) todetect occupancy in the entire room. Such sensors and respective controldevices for the given room may be configured such that the same controldevices are responsive to both sensors and in particular, eachrespective device is configured/controlled to react the same (e.g., dimsto the same level) regardless of which sensor detects an occupancycondition. In addition, the sensors may be configured the same (e.g., asan occupancy sensor, as a vacancy sensor, etc.). According to thisexample, if a given room is configured in this manner, the controlapplication may only display one icon representing the multiple sensors.For example, the icon may be shown in one color/contrast when neithersensor detects occupancy and shown in another color/contrast when atleast one or both of the sensors detects occupancy. As another example,selecting the icon to configure the sensors may show the configurationinterfaces as discussed below as if there is one sensor, with thecontrol application/system controller subsequently configuring bothsensors the same. Other variations are possible including displayingmultiple sensor icons for each sensor in this latter example. Inaddition, one will recognize that not all lighting control devices shownin pain 1784 (including all or none) may be responsive to signals from agiven sensor. Similarly, assuming all lighting control devicesrepresented by the icons 1732 a, 1732 b are responsive to signals fromthe occupancy sensor(s), each of the icons may indicate that itsrespective lighting control device is off and occupancy indicator 1724 astill be displayed by the control application, thereby showing the roomis occupied. As discussed above, upon detecting/determining that theuser has once again activated/selected carrot/icon 808 of pain 1784, thecontrol application may contract the pain as shown in FIG. 9A.

In general, by notifying a user that the Living Room, for example, isoccupied or vacant through the use of an occupancy indicator asdescribed herein, the user may now make a more educated decision as towhether to use the control application to turn lighting controldevices/lights, for example, in the room on or off, for example, via thecontrol application (or to control other control devices/loads such asfans, shades, HVAC, music, etc.). This may be especially advantageous ifthe user is using the control application from a location remote fromthe Living Room. For example, without the use of the occupancy indicatoras described herein, the user may note through the control applicationthat the Living Room lights are on, and decide to turn them off to saveenergy, for example, even though a person may be in the room. Throughthe use of the occupancy indicator, the user can now make a moreeducated decision and possibly not turn the lights off via theapplication knowing a person may be in the room.

Turning to FIG. 9C, there is shown an example of the 1^(st) FloorBathroom pain 1788 expanded as a result of the control applicationdetecting an actuation of carrot/icon 808 of the pain. Similar to FIG.9B, in this example two icons 1734 a, 1734 b are shown representing twolighting control devices (a “Vanity Lights” and a “Ceiling Lights”). Inthis example, icon 1734 b is shown to indicate that the Vanity Lightscontrol device/lighting load is on. Icon 1734 a is shown to indicatethat the Ceiling Lights control device/lighting load is off. As furthershown in this example, pain 1788 also includes an icon 1734 crepresenting the occupancy sensor(s) located in the 1^(st) FloorBathroom. Similar to the occupancy sensor icon 1732 c, the controlapplication may further associate with icon 1734 c an indication orlabel (here “Occupancy Sensor”) to provide further information about thesensor. As shown in this example, the control application may continueto display the occupancy indicator 1724 b when the pain is expanded toshow the room is occupied. As the occupancy/vacancy condition within the1^(st) Floor Bathroom changes, the control application may receive fromthe system controller 250 a an indication of this change and update pane1788 to either show or remove the occupancy indicator 1724 b, asappropriate.

Similar to the occupancy sensor icon 1732 c of FIG. 9B, occupancy sensoricon 1734 c may be selectable to allow a user to control/configureand/or test the occupancy sensor and/or the lighting control devices thesensor is configured to control. For example, assuming the controlapplication detects/determines that a user selects icon 1734 c in pain1788, the control application may display a control interface 1712 asshown in FIG. 9D. Control interface 1712 may be shown alone orsuperimposed over interface 1710 of FIG. 9C, for example. One willrecognize that control interface 1712 is an example and other controlinterface configurations are possible. According to this example,control interface 1712 may have three actuators (shown here as buttonsfor example), including actuator 1742 (labeled “Test Occupied”),actuator 1744 (labeled “Test Unoccupied”), and actuator 1746 (labeled“Edit Device”). One will recognize that other and/or additionalactuators are possible. Actuators 1742 and 1744 may allow a user to testthe configuration of the sensor and lighting control devices, forexample, that may be responsive to signals communicated by the sensor.Actuator 1746 may allow a user to configure the sensor and the lightingcontrol devices, for example, that may be responsive to signalscommunicated by the sensor. (Again, if icon 1732 c represents multiplesensors, interface 1712 and the interfaces shown in FIGS. 9E and 9F mayresult in both sensors being tested and configured at the same time.Alternatively, the control application may display interfaces thatallows the user to test and configure the sensors individually).Assuming icon 1734 c represents one sensor, for example, in response todetecting selection of actuator 1742 by a user, the control applicationmay communicate one or more messages to the system controller 250 a toinstruct the controller to configure or instruct the occupancy sensor inthe 1^(st) Floor Bathroom to enter an occupancy state (if not alreadythere) and to communicate an occupancy signal(s). In response to theoccupancy signal(s), any lighting control device in the 1^(st) FloorBathroom that is configured to be responsive to an occupancy signal fromthe sensor may cause its corresponding lighting load to turn on, if notalready on, for example (or go to a specific dimming level, for example,depending on the configuration of the device). If a lighting controldevice changes from an off state to an on state as a result of the test,the control application may receive an indication of this change fromthe system controller and may reflect the change in the control devicesicon(s) 1734 a, 1734 b (e.g., by changing their color/contrast) in pain1788 when the user returns to interface 1710, for example, and mayincrement the count shown in connection with icon 1722, for example.Similarly, if the sensor is in a vacancy state prior to the test andchanges to an occupancy state, the control application may receive anindication of this change from the system controller and may reflect thechange by displaying an occupancy indicator 1724 b in graphical userinterface 1710 of FIGS. 9A and 9B, for example. Subsequent to detectingselection of actuator 1742, the control application may again displaygraphical user interface 1710 of FIG. 9B, for example. As anotherexample, a user may touch an area outside of interface 1746, which maycause the control application to return interface 1710 of FIG. 9B, forexample. Other variations are possible.

Similarly, in response to detecting selection of actuator 1744 by auser, the control application may communicate one or more messages tothe system controller 250 a to instruct the controller to configure orinstruct the occupancy sensor in the 1^(st) Floor Bathroom to enter avacancy state (if not already there) and to communicate a vacancysignal(s) for example. In response to the vacancy signal(s), anylighting control device in the 1^(st) Floor Bathroom that is configuredto be responsive to a vacancy signal from the sensor may cause itscorresponding lighting load to turn off, if not already off, for example(or go to a reduced dimming level, for example, depending on theconfiguration of the device). If a lighting control device changes froman on state to an off state, the control application may receive anindication of this change from the system controller and may reflect thechange in the control devices icon(s) 1734 a, 1734 b (e.g., by changingtheir color/contrast) in pain 1788 when the user returns to interface1710, for example, and may decrement the count shown in connection withicon 1722, for example. Similarly, if the sensor is in an occupancystate prior to the test and thus changes to a vacancy state, the controlapplication may receive an indication of this change from the systemcontroller and may reflect the change by removing the occupancyindicator 1724 b in graphical user interface 1710 of FIGS. 9A and 9B,for example. Subsequent to detecting selection of actuator 1744, thecontrol application may again display graphical user interface 1710 ofFIG. 9B, for example, although again, other variations are possible.

Regarding the Edit Device actuator 1746, in response todetecting/determining that the user selects the actuator, the controlapplication may display a control interface 1714 as shown in FIG. 9E.One will recognize that control interface 1714 is an example and othercontrol interface configurations are possible. According to thisexample, control interface 1714 may provide a field 1750 that may allowa user to change the label (“Occupancy Sensor”) associated with thesensor icon 1734 c when displayed in the expanded view of pain 1788 ofFIG. 9B, for example. Control interface 1714 may further include aselectable actuator or icon 1752 that allows a user to further configurethe sensor and lighting control devices, for example, that may beresponsive to signals communicated by the sensor. Control interface 1714may further include a selectable actuator or icon 1751 that causes thecontrol application to display sensor operating instructions (notshown). Control interface 1714 may also include a selectable actuator oricon 1753 that causes the control application to display a controlinterface (not shown) that allows a user to further configure the loadcontrol system to note the addition or removal of control devices (suchas the addition of more lights) to the bathroom. Control interface 1714may also include a selectable actuator 1756 that allows a user to removethe sensor from the load control system.

With respect to actuator 1752, in response to detecting/determining thata user selects actuator 1752 the control application may display acontrol interface 1716 as shown in FIG. 9F. One will recognize thatcontrol interface 1716 is an example and other control interfaceconfigurations are possible. According to one example, the controlapplication may display in control interface 1716 a respective pane 1760and 1761 for each lighting control device in the 1^(st) Floor Bathroomthat is configurable to be responsive to the sensor. The controlapplication may make this determination of what control devices todisplay based on configuration information received from the systemcontroller 250 a. In this example, it is assumed that both the VanityLights and the Ceiling Lights are configurable to be responsive to thesensor and each therefore has a respective pane 1760 and 1761 in theinterface. The control application may expand and contract each of panes1760 and 1761 in response to an actuation of a respective carrot or icon1762. Further, interface 1716 may be scrollable up and down. For ease ofdescription, each of panes 1760 and 1761 is shown as being expanded inthis example and are shown together on network device 680. According toa further example, the control application may customize each of panes1760 and 1761 based on the capabilities of the respective lightingcontrol device the pane corresponds to. For example, the Vanity Lightsmay be dimmable and as such, pane 1760 may be shown as having dimmingcontrols (as shown here). The Ceiling Lights may be switched andaccordingly, pane 1761 may be shown as having on/off based controls (asshown here). Again, the control application may make this determinationas to the types of controls to display based on configurationinformation received from the system controller 250 a. In this example,the sensor of the 1^(st) Floor Bathroom is assumed to be configured asan occupancy/vacancy sensor. If the sensor were only a vacancy sensor,panes 1760 and 1761 may be configured to only configure vacancyconditions. Again, the control application may make this determinationbased on information received from the system controller 250 a.

Turning to pane 1760 as an example, it may include a selectableactuator/field 1767. This actuator may allow a user (e.g., throughselection and un-selection) to configure the control system 210 a suchthat the Vanity Lights are either non-responsive or responsive ingeneral to the sensor. Assuming field 1767 is selected as here, pane1760 may also include a selectable actuator/field 1763 (labeled“Unaffected” here as an example). This actuator may allow a user (e.g.,through selection and un-selection) to configure the control system 210a such that the Vanity Lights are either non-responsive or responsive tooccupancy signals from the sensor. Assuming the Vanity Lights areconfigured to be responsive to occupancy signals (as in this example),pane 1760 may include an actuator 1764 (here a slide control andselectable buttons) that allows a user to set the dimming level theVanity Lights should go to (e.g., a range from “off” to 100% “on”) inresponse to an occupancy signal. Pane 1760 may further include anactuator/field 1765 (labeled “Unaffected” here as an example). Thisactuator may allow a user (e.g., through selection and un-selection) toconfigure the control system 210 a such that the Vanity Lights areeither non-responsive or responsive to vacancy signals from the sensor.Assuming the Vanity Lights are configured to be responsive to vacancysignals (as in this example), pane 1760 may include an actuator 1766(here a slide control and selectable buttons) that allows a user to setthe dimming level the Vanity Lights should go to (e.g., a range from“off” to 100% “on”) in response to a vacancy signal. In this example,the Vanity Lights are configured to be responsive to go to 100% on inresponse to occupancy signals and to go off in response to vacancysignals.

Pane 1761 may be similarly configured as pane 1760. For example, pane1761 may include a selectable actuator/field 1772. This actuator mayallow a user (e.g., through selection and un-selection) to configure thecontrol system 210 a such that the Ceiling Lights are eithernon-responsive or responsive in general to the sensor. Assuming field1772 is selected as here, pane 1761 may also include an actuator/field1768 (labeled “Unaffected” here as an example). This actuator may allowa user (through selection and un-selection) to configure the controlsystem 210 a such that the Ceiling Lights are either non-responsive orresponsive to occupancy signals from the sensor. In this example, theCeiling Lights are configured to be non-responsive to occupancy signalsfrom the sensor. Assuming the Ceiling Lights were configured to beresponsive to occupancy signals, pane 1761 may activate an actuator 1769(here selectable buttons and shown as un-activated) that may allow auser to cause the lights to either turn on or turn off in response to anoccupancy signal. Pane 1761 may further include an actuator/field 1770(labeled “Unaffected” here as an example). This actuator may allow auser (through selection and un-selection) to configure the controlsystem 210 a such that the Ceiling Lights are either non-responsive orresponsive to vacancy signals from the sensor. Assuming the VanityLights are configured to be responsive to vacancy signals (as in thisexample), pane 1761 may include an actuator 1771 (here selectablebuttons) that allows a user to cause the Ceiling Lights to either turnon or turn off in response to a vacancy signal. In this example, theCeiling Lights are configured to turn off in response to vacancysignals.

Control interface 1716 may further include an actuator 1773, actuationof which by a user may cause the control application to display controlinterface 1714 of FIG. 9E. Control interface 1714 may include anactuator 1754 (here, labeled “Save” as an example). Selection ofactuator 1754 may cause the control application to communicate to thesystem controller one more messages reflecting any changes (e.g.,configuration settings) made in control interfaces 1714 and/or 1716. Thesystem controller 250 a may then reconfiguring the control device(s) asnecessary. Thereafter, the control application may again displaygraphical user interface 1710 of FIG. 9B, for example. Similarly,control interface 1714 may include an actuator 1755 (here, labeled“Cancel” as an example). Selection of actuator 1755 may cause thecontrol application to disregard the changes made in control interfaces1714 and/or 1716 and to display graphical user interface 1710 of FIG.9B, for example. Again, this is an example and other configurations arepossible.

Turning again to FIG. 9A, upon detecting/determining that the user hasselected lighting devices icon 1722, the control application may displayto the user via network device 680 the graphical user interface 1718 asshown in FIG. 9G. FIG. 9G is similar to graphical user interface 702 ofFIG. 6C, for example, and may function as similarly described forgraphical user interface 702. Interface 1718 may include a respectivecontrol device icon 1780 for each lighting control device havinglighting load(s) that are currently on. According to this example, foreach room (here the Living Room) having an occupancy sensor that is inan occupancy state, the respective icons for the lighting controldevices may include an additional occupancy indicator 1781 (here aperson icon, although other icons or indicators may be used) to showthat the respective room is occupied. According to one example, only theicons for the lighting control devices that are responsive to occupancyand/or vacancy signals from the sensor may include occupancy indicator1781. According to another example, even if a lighting control device isnot responsive to occupancy and/or vacancy signals from the sensor, theicon for the device may include the occupancy indicator 1781. Assimilarly discussed for graphical user interface 702, as a lightingcontrol device turns its respective load(s) on, the control applicationmay receive an indication of this change from the system controller 250a and display to the user an additional icon 1780 in interface 1718 thatis associated with the lighting control device. That icon may or may notinclude indicator 1781 based on the occupancy condition of the room, forexample. Similarly, as a lighting device turns its respective load(s)off, the control application may receive an indication of this changefrom the system controller 250 a and remove from interface 702 the icon706 associated with the device. Similarly, if an occupancy sensorchanges from an occupied state to a vacancy/vacant state, the controlapplication may receive an indication of this change from the systemcontroller 250 a and change respective lighting control device icons1780 to remove icon 1781. Similarly, if an occupancy sensor changes froma vacancy/vacant state to an occupied state, the control application mayreceive an indication of this change from the system controller 250 aand change respective lighting control device icons 1780 to add icon1781. Other ways of showing occupancy in interface 7118 are possible. Inthis example, the Kitchen does not include an occupancy sensor and thusno occupancy indicator may be shown with respective icons of the Kitchencontrol devices.

In general, by notifying a user via interface 1718 that certain lightsin certain rooms are on and that these rooms may be occupied asdescribed herein, the user may now make a more educated decision as towhether to use the control application to turn lights in such rooms offvia the control application. This may be especially advantageous if theuser is using the control application from a location remote from userenvironment. For example, without the use of the occupancy indicator asdescribed herein, the user may note through the control application thatcertain lights are on, and decide to turn them off to save energy, forexample, even though a person may be in the room. Through the use of theoccupancy indicator, the user can now make a more educated decision andpossibly not turn the lights off via the application knowing a personmay be in the room.

In addition to the examples shown in FIGS. 9A-9G, occupancy indictorsmay be shown in other interfaces discussed herein in a similar fashionas shown FIGS. 9A-9G. The occupancy indictors may also be associatedwith icons for other control devices (e.g., fan devices, shade devices,audio devices, and thermostat devices) even if the device is notresponsive to a sensor but is located in a room with a sensor. Forexample, interfaces that include an indication of a room(s) orlocation(s) or space(s) in a user environment such as those shown inFIGS. 6A-6Q, 6T, 6Y-6Z, 7A-7B, and 8A-8D may include occupancy and/orvacancy indicators.

One will recognize that tabs 642, 644, and 646 of the graphicalinterfaces shown in FIGS. 6A, 6O, 6Y, and 6Z, and FIGS. 7A-9C forexample, may be shown in different orders. For example, the graphicalinterfaces describe herein have the Devices tab 642 is shown first, theScenes tab 644 second to the right of the Devices tab, and the Schedulestab 646 shown third to the right of the Scenes tab. Nonetheless, thetabs may be displayed in other orders. In addition, any of the tabs maybe the default tab. Nonetheless, a user may desire to control certaindevices in certain rooms. Hence, having the Devices tab 642 positionedfirst as shown herein and being the default tab may make this tab moreeasily accessible to the user.

In addition, the placement of section 620 and selectable tabs 642, 644,and 646 on a single interface like that shown in FIGS. 6A, 6O, 6Y, and6Z, and FIGS. 7A-9C for example may be advantageous in that thesefunctions and related features may be typical functions and features auser may use when accessing the control application.

Furthermore, the amount of information and/or the number of icons forexample shown in the example interfaces herein (such as the number oficons in section 620 and the number of panes and icons shown in section660 when the Devices tab 642 is active) may vary based on the type ofnetwork device 680 running the control application. For example, whenthe control application described herein runs on a phone, theapplication may display a first amount of information in any giveninterface; and when the control application described herein runs on atablet for example that may have a larger display screen than the phone,the application may display a second amount of information in any giveninterface that is greater than the first amount. Alternatively and/or inaddition, the information and/or icons for example in any giveninterface may be displayed in a different fashion based on the type ofdevice. For example, on a phone, icons within a pane of section 660 whenthe Devices tab 642 is active may be shown in a number of rows.Alternatively, those same icons on a tablet for example may fit in onerow or a fewer number of rows. Similarly, for devices that may havedisplay screens with different length-width measurements and that maydetect orientation, as a user re-orients the device the controlapplication may reformat the information and/or icons based on thechanging orientation. Other examples are possible.

FIG. 13 is a block diagram illustrating another example systemcontroller 1200 (such as system controller 150 and 250 a/250 b,described herein). The system controller 1200 may include one or moregeneral purpose processors, special purpose processors, conventionalprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, integrated circuits, programmable logic devices (PLD),field programmable gate arrays (FPGA), application specific integratedcircuits (ASICs), or any suitable controller or processing device or thelike (hereinafter collectively referred to as processor(s) or controlcircuit(s) 1202). The control circuit 1202 may be configured to executeone or more software-based applications that include instructions thatwhen executed by the control circuit may configure the control circuitto perform signal coding, data processing, power control, input/outputprocessing, or any other function, process, and/or operation for examplethat enables the system controller 1200 to perform as described herein.One will recognize that functions, features, processes, and/oroperations described herein of the system controller 1200 may alsoand/or alternatively be provided by firmware and/or hardware in additionto and/or as an alternative to software-based instructions. The controlcircuit 1202 may store information in and/or retrieve information fromthe memory 1204, including configuration information/configurationinformation file(s), backup file(s), creation times, and signature(s) asdescribed herein. Memory 1204 may also store software-based instructionsfor execution by the control circuit 1202 and may also provide anexecution space as the control circuit executes instructions. Memory1204 may be implemented as an external integrated circuit (IC) or as aninternal circuit of the control circuit 1202. Memory 1204 may includevolatile and non-volatile memory modules/devices and may benon-removable memory modules/devices and/or a removable memorymodules/devices. Non-removable memory may include random-access memory(RAM), read-only memory (ROM), a hard disk, or any other type ofnon-removable memory storage. Removable memory may include a subscriberidentity module (SIM) card, a memory stick, a memory card, or any othertype of removable memory. One will appreciate that the memory used tostore configuration information file(s), and/or backup file(s), and/orsoftware-based instructions, etc. may be the same and/or differentmemory modules/devices of the system controller. As one example,configuration information file(s) and software-based instructions may bestored in non-volatile memory modules/devices while backup(s) may bestored in volatile and/or non-volatile memory modules/devices.

The system controller 1200 may include one or more communicationscircuits/network interface devices or cards 1206 for transmitting and/orreceiving information. The communications circuit 1206 may performwireless and/or wired communications. The system controller 1200 mayalso, or alternatively, include one or more communicationscircuits/network interface devices/cards 1208 for transmitting and/orreceiving information. The communications circuit 1206 may performwireless and/or wired communications. Communications circuits 1206 and1208 may be in communication with control circuit 1202. Thecommunications circuits 1206 and/or 1208 may include radio frequency(RF) transceivers or other communications modules configured to performwireless communications via an antenna(s). The communications circuit1206 and communications circuit 1208 may be configured to performcommunications via the same communication channels or differentcommunication channels. For example, the communications circuit 1206 maybe configured to communicate (e.g., with a network device, over anetwork, etc.) via a wireless communication channel (e.g., BLUETOOTH®,near field communication (NFC), WIFI®, WI-MAX®, cellular, etc.) and thecommunications circuit 1208 may be configured to communicate (e.g., withcontrol devices and/or other devices in the load control system) viaanother wireless communication channel (e.g., WI-FI®, Zigbee, Thread,etc., or a proprietary communication channel, such as CLEAR CONNECT™).

The control circuit 1202 may be in communication with an LEDindicator(s) 1212 for providing indications to a user. The controlcircuit 1202 may be in communication with an actuator(s) 1214 (e.g., oneor more buttons) that may be actuated by a user to communicate userselections to the control circuit 1202. For example, the actuator 1214may be actuated to put the control circuit 1202 in an association modeand/or communicate association messages from the system controller 1200.

Each of the modules within the system controller 1200 may be powered bya power source 1210. The power source 1210 may include an AC powersupply or DC power supply, for example. The power source 1210 maygenerate a supply voltage V_(CC) for powering the modules within thesystem controller 1200. One will recognize that system controller 1200may include other, fewer, and/or additional modules.

FIG. 14 is a block diagram illustrating an example control-target device1300, e.g., a load control device, as described herein. Thecontrol-target device 1300 may be a dimmer switch, an electronic switch,an electronic ballast for lamps, an LED driver for LED light sources, anAC plug-in load control device, a temperature control device (e.g., athermostat), a motor drive unit for a motorized window treatment, orother load control device. The control-target device 1300 may includeone or more communications circuits/network interface devices or cards1302. The communications circuit 1302 may include a receiver, an RFtransceiver, and/or other communications module configured to performwired and/or wireless communications via communications link 1310. Forexample, the communications circuit 1302 may be configured tocommunicate (e.g., with a network device, over a network, etc.) via afirst wireless communication channel (e.g., BLUETOOTH®, near fieldcommunication (NFC), WIFI®, WI-MAX®, cellular, etc.) and may be furtherconfigured to communicate (e.g., with control source devices, a systemcontroller, and/or other devices in the load control system) via anotherwireless communication channel (e.g., WI-FI®, Zigbee, Thread, etc., or aproprietary communication channel, such as CLEAR CONNECT™). Thecontrol-target device 1300 may include one or more general purposeprocessors, special purpose processors, conventional processors, digitalsignal processors (DSPs), microprocessors, microcontrollers, integratedcircuits, programmable logic devices (PLD), field programmable gatearrays (FPGA), application specific integrated circuits (ASICs), or anysuitable controller or processing device or the like (hereinaftercollectively referred to as processor(s) or control circuit(s) 1304).The control circuit 1304 may be configured to execute one or moresoftware-based applications that include instructions that when executedby the control circuit may configure the control circuit to performsignal coding, data processing, power control, input/output processing,or any other function, feature, process, and/or operation for examplethat enables the control-target device 1300 to perform as describedherein. One will recognize that functions, features, processes, and/oroperations, described herein for the control-target device 1300 may alsoand/or alternatively be provided by firmware and/or hardware in additionto and/or as an alternative to software-based instructions. The controlcircuit 1304 may store information in and/or retrieve information fromthe memory 1306. For example, the memory 1306 may maintain a registry ofassociated control devices and/or control configuration information.Memory 1306 may also store software-based instructions for execution bythe control circuit 1304 and may also provide an execution space as thecontrol circuit executes instructions. Memory 1306 may be implemented asan external integrated circuit (IC) or as an internal circuit of thecontrol circuit 1304. Memory 1306 may include volatile and non-volatilememory modules/devices and may be non-removable memory modules/devicesand/or a removable memory modules/devices. Non-removable memory mayinclude random-access memory (RAM), read-only memory (ROM), a hard disk,or any other type of non-removable memory storage. Removable memory mayinclude a subscriber identity module (SIM) card, a memory stick, amemory card, or any other type of removable memory. The control circuit1304 may also be in communication with the communications circuit 1302.

The control-target device 1300 may include a load control circuit 1308.The load control circuit 1308 may receive instructions from the controlcircuit 1304 and may control an electrical load 1316 based on thereceived instructions. The load control circuit 1308 may send statusfeedback to the control circuit 1304 regarding the status of theelectrical load 1316. The load control circuit 1308 may receive powervia a hot connection 1312 and a neutral connection 1314 and may providean amount of power to the electrical load 1316. The electrical load 1316may include any type of electrical load.

The control circuit 1304 may be in communication with an actuator 1318(e.g., one or more buttons) that may be actuated by a user tocommunicate user selections to the control circuit 1304. For example,the actuator 1318 may be actuated to put the control circuit 1304 in anassociation mode or discovery mode and may communicate associationmessages or discovery messages from the control-target device 1300. Onewill recognize that control-target device 1300 may include other, fewer,and/or additional modules.

FIG. 15 is a block diagram illustrating an example control-source device1400 as described herein. The control-source device 1400 may be a remotecontrol device, an occupancy sensor, a daylight sensor, a window sensor,a temperature sensor, and/or the like. The control-source device 1400may include one or more general purpose processors, special purposeprocessors, conventional processors, digital signal processors (DSPs),microprocessors, microcontrollers, integrated circuits, programmablelogic devices (PLD), field programmable gate arrays (FPGA), applicationspecific integrated circuits (ASICs), or any suitable controller orprocessing device or the like (hereinafter collectively referred to asprocessor(s) or control circuit(s) 1402). The control circuit 1402 maybe configured to execute one or more software-based applications thatinclude instructions that when executed by the control circuit mayconfigure the control circuit to perform signal coding, data processing,power control, input/output processing, or any other function, feature,process, and/or operation for example that enables the control-sourcedevice 1400 to perform as described herein. One will recognize thatfunctions, features, processes, and/or operations described herein forthe control-source device 1400 may also and/or alternatively be providedby firmware and/or hardware in addition to and/or as an alternative tosoftware-based instructions. The control circuit 1402 may storeinformation in and/or retrieve information from the memory 1404. Memory1404 may also store software-based instructions for execution by thecontrol circuit 1402 and may also provide an execution space as thecontrol circuit executes instructions. Memory 1404 may be implemented asan external integrated circuit (IC) or as an internal circuit of thecontrol circuit 1402. Memory 1404 may include volatile and non-volatilememory modules/devices and may be non-removable memory modules/devicesand/or a removable memory modules/devices. Non-removable memory mayinclude random-access memory (RAM), read-only memory (ROM), a hard disk,or any other type of non-removable memory storage. Removable memory mayinclude a subscriber identity module (SIM) card, a memory stick, amemory card, or any other type of removable memory.

The control-source device 1400 may include one or more communicationscircuits/network interface devices or cards 1408 for transmitting and/orreceiving information. The communications circuit 1408 may transmitand/or receive information via wired and/or wireless communications viacommunications circuit 1408. The communications circuit 1408 may includea transmitter, an RF transceiver, and/or other circuit configured toperform wired and/or wireless communications. For example, thecommunications circuit 1408 may be configured to communicate (e.g., witha network device, over a network, etc.) via a first wirelesscommunication channel (e.g., BLUETOOTH®, near field communication (NFC),WIFI®, WI-MAX®, cellular, etc.) and may be further configured tocommunicate (e.g., with control target devices, a system controller,and/or other devices in the load control system) via another wirelesscommunication channel (e.g., WI-FI®, Zigbee, Thread, etc., or aproprietary communication channel, such as CLEAR CONNECT™). Thecommunications circuit 1408 may be in communication with control circuit1402 for transmitting and/or receiving information.

The control circuit 1402 may also be in communication with an inputcircuit(s) 1406. The input circuit 1406 may include an actuator(s)(e.g., one or more buttons) and/or a sensor circuit (e.g., an occupancysensor circuit, a daylight sensor circuit, or a temperature sensorcircuit) for receiving input that may be sent to a control-target devicefor controlling an electrical load. For example, the control-sourcedevice may receive input from the input circuit 1406 to put the controlcircuit 1402 in an association mode and/or communicate associationmessages from the control-source device. The control circuit 1402 mayreceive information from the input circuit 1406 (e.g., an indicationthat a button has been actuated or sensed information). Each of themodules within the control-source device 1400 may be powered by a powersource 1410. One will recognize that control-source device 1400 mayinclude other, fewer, and/or additional modules.

In addition to what has been described herein, the methods and systemsmay also be implemented in a computer program(s), software, or firmwareincorporated in one or more computer-readable media for execution by acomputer(s) or processor(s), for example. Examples of computer-readablemedia include electronic signals (transmitted over wired or wirelessconnections) and tangible/non-transitory computer-readable storagemedia. Examples of tangible/non-transitory computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom-access memory (RAM), removable disks, and optical media such asCD-ROM disks, and digital versatile disks (DVDs).

While this disclosure has been described in terms of certain embodimentsand generally associated methods, alterations and permutations of theembodiments and methods will be apparent to those skilled in the art.Accordingly, the above description of example embodiments does notconstrain this disclosure. Other changes, substitutions, and alterationsare also possible without departing from the spirit and scope of thisdisclosure.

What is claimed is:
 1. An apparatus comprising: a display screen; acommunications circuit; at least one processor; and at least one memorydevice communicatively coupled to the at least one processor and havingsoftware instructions stored thereon that when executed by the at leastone processor, direct the at least one processor to: receive via thecommunications circuit from a communications network informationcommunicated by a controller, wherein the controller is configured tocommunicate with a lighting control device, wherein the lighting controldevice is configured to control a lighting load, wherein the lightingload is configured to produce light of any of a plurality of differentcolors, and wherein the information comprises an indication of a colorthe lighting load is configured to produce; display on the displayscreen a graphical user interface that comprises an on-off actuator toturn the lighting load on and off; and display together with the on-offactuator in the graphical user interface a color indicator thatindicates the color the lighting load is configured to produce.
 2. Theapparatus of claim 1, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to:detect an actuation of the on-off actuator to turn the lighting loadoff; and responsive to detecting the actuation of the on-off actuator toturn the lighting load off, remove from the graphical user interface thecolor indicator.
 3. The apparatus of claim 1, wherein the instructions,when executed by the at least one processor, further direct the at leastone processor to: display within the graphical user interface a dimmingactuator to change an intensity level of the lighting load; detect anactuation of the dimming actuator to change the lighting load to a newintensity level; and responsive to detecting the actuation of thedimming actuator to change the lighting load to the new intensity level,communicate a message to the controller to control the lighting load tothe new intensity level.
 4. The apparatus of claim 3, wherein to displaywithin the graphical user interface the dimming actuator comprises todisplay the dimming actuator on a control line such that a position ofthe dimming actuator on the control line shows an intensity level of thelighting load.
 5. The apparatus of claim 3, wherein the instructions,when executed by the at least one processor, further direct the at leastone processor to: display within the graphical user interface a pallettogether with the dimming actuator, wherein the pallet enable selectionof a color; detect a selected color on the pallet; and responsive todetecting the selected color on the pallet, communicate a message to thecontroller to control the lighting load to the selected color.
 6. Theapparatus of claim 5, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to:display within the graphical user interface the color indicator togetherwith the dimming actuator and the pallet; and responsive to detectingthe selected color on the pallet, change the color indicator to indicatethe selected color.
 7. The apparatus of claim 6, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: prior to detecting the selectedcolor on the pallet, display the color indicator as having a first sizein the graphical user interface; and responsive to detecting theselected color on the pallet, increase within the graphical userinterface a size of the color indicator to a second size that is greaterthan the first size.
 8. The apparatus of claim 7, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: subsequent to increasing the sizeof the indicator to the second size, decrease within the graphical userinterface the size of the color indicator from the second size to thefirst size.
 9. The apparatus of claim 5, wherein the lighting loadcomprises a plurality of light emitting diodes (LEDs) including a whiteor a substantially white LED; and wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: display a vibrancy actuator; detect an actuation of thevibrancy actuator; and responsive to detecting the actuation of thevibrancy actuator, communicate a message to the controller to controlthe lighting load to reduce an intensity of the white or thesubstantially white LED while continuing to produce the color thelighting load is configured to produce.
 10. The apparatus of claim 9,subsequent to detecting the actuation of the vibrancy actuator, detect afurther actuation of the vibrancy actuator; and responsive to detectingthe further actuation of the vibrancy actuator, communicate a message tothe controller to control the lighting load to increase the intensity ofthe white or the substantially white LED while continuing to produce thecolor the lighting load is configured to produce.
 11. The apparatus ofclaim 5, wherein the pallet enables selection of a color only along ablack body curve.
 12. The apparatus of claim 5, wherein the lightingload comprises a plurality of light emitting diodes (LEDs) of aplurality of different colors; and wherein the pallet enables selectionof a color within color gamut formed by the plurality of differentcolored LEDs.
 13. The apparatus of claim 1, wherein the instructions,when executed by the at least one processor, further direct the at leastone processor to: display within the graphical user interface a dimmingactuator to change an intensity of the lighting load, a warm-coolactuator to configure the lighting load to produce a color on a blackbody curve, and a full-color actuator to configure the lighting load toproduce a color within a color gamut comprising additional colors notfound on the black body curve.
 14. The apparatus of claim 13, whereinthe instructions, when executed by the at least one processor, furtherdirect the at least one processor to: detect an actuation of the dimmingactuator to change the lighting load to a new intensity level; andresponsive to detecting the actuation of the dimming actuator by theuser to change the lighting load to the new intensity level, communicatea message to the controller to control the lighting load to the newintensity level.
 15. The apparatus of claim 13, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: detect an actuation of thewarm-cool actuator; responsive to detecting the actuation of thewarm-cool actuator, display on the display screen a pallet together withthe dimming actuator, wherein the pallet enables selection of a color onthe black body curve; detect a selected color on the pallet; andresponsive to detecting the selected color on the pallet, communicate amessage to the controller to control the lighting load to the selectedcolor.
 16. The apparatus of claim 15, wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: prior to detecting the selected color on the pallet,display in the graphical user interface the color indicator asindicating a first color and having a first size; and responsive todetecting the selected color on the pallet, change within the graphicaluser interface the color indicator from indicating the first color toindicate the selected color, and increase within the graphical userinterface a size of the color indicator to a second size that is greaterthan the first size.
 17. The apparatus of claim 13, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: detect an actuation of thefull-color actuator; responsive to detecting the actuation of thefull-color actuator, display on the display screen a pallet togetherwith the dimming actuator, wherein the pallet enables selection of acolor on the color gamut; detect a selected color on the pallet; andresponsive to detecting the selected color on the pallet, communicate amessage to the controller to control the lighting load to the selectedcolor.
 18. The apparatus of claim 17, wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: prior to detecting the selected color on the pallet,display in the graphical user interface the color indicator asindicating a first color and having a first size; and responsive todetecting the selected color on the pallet, change within the graphicaluser interface the color indicator from indicating first color toindicate the selected color, and increase within the graphical userinterface a size of the color indicator to a second size that is greaterthan the first size.
 19. The apparatus of claim 13, wherein the lightingload comprises a plurality of light emitting diodes (LEDs); and whereinthe instructions, when executed by the at least one processor, furtherdirect the at least one processor to: display a vibrancy actuatortogether with the dimming actuator, the warm-cool actuator, and thefull-color actuator; detect an actuation of the vibrancy actuator; andresponsive to detecting the actuation of the vibrancy actuator,communicate a message to the controller to control the lighting load toreduce an intensity of at least one of the plurality of LEDs whilecontinuing to produce the color the lighting load is configured toproduce.
 20. The apparatus of claim 19, subsequent to detecting theactuation of the vibrancy actuator, detect a further actuation of thevibrancy actuator; and responsive to detecting the further actuation ofthe vibrancy actuator, communicate a message to the controller tocontrol the lighting load to increase an intensity of at least one ofthe plurality of LEDs while continuing to produce the color the lightingload is configured to produce.
 21. The apparatus of claim 1, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: display within the graphical userinterface a pallet together with the color indicator, wherein the palletenables selection of a color; detect a selected color on the pallet; andresponsive to detecting the selected color on the pallet, communicate amessage to the controller to control the lighting load to the selectedcolor.
 22. The apparatus of claim 21, wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: responsive to detecting the selected color on the pallet,change within the graphical user interface the color indicator toindicate the selected color.
 23. The apparatus of claim 21, wherein theinstructions, when executed by the at least one processor, furtherdirect the at least one processor to: display within the graphical userinterface an auto actuator that, when enabled, causes the lighting loadto produce light at a color rendering index (CRI) value that is greaterthan or equal to a CRI value threshold; and determine that the autoactuator is enabled; and wherein to communicate the message to thecontroller to control the lighting load to the selected color comprisesto communicate the message to the controller to control the lightingload to the selected color and to further control the lighting load,based on the auto actuator being enabled, to a color rendering index(CRI) value that is greater than or equal to the CRI value threshold.24. The apparatus of claim 23, wherein the instructions, when executedby the at least one processor, further direct the at least one processorto: determine that the auto actuator is disabled; responsive todetermining that the auto actuator is disabled, display within thegraphical user interface a vibrancy actuator to change a vibrancy levelof the lighting load; detect an actuation of the vibrancy actuator tochange the lighting load to a new vibrancy level; and responsive todetecting the actuation of the vibrancy actuator to change the lightingload to the new vibrancy level, communicate a message to the controllerto control the lighting load to the new vibrancy level.
 25. Anon-transitory tangible computer readable medium having instructionsstored thereon that when executed by at least one processor direct theat least one processor to: receive via a communications circuit from acommunications network information communicated by a controller, whereinthe controller is configured to communicate with a lighting controldevice, wherein the lighting control device is configured to control alighting load, wherein the lighting load is configured to produce lightof any of a plurality of different colors, and wherein the informationcomprises an indication of a color the lighting load is configured toproduce; display on a display screen a graphical user interface thatcomprises an on-off actuator to turn the lighting load on and off; anddisplay together with the on-off actuator in the graphical userinterface a color indicator that indicates the color the lighting loadis configured to produce.
 26. A method comprising: receiving by at leastone processor via a communications circuit from a communications networkinformation communicated by a controller, wherein the controller isconfigured to communicate with a lighting control device, wherein thelighting control device is configured to control a lighting load,wherein the lighting load is configured to produce light of any of aplurality of different colors, and wherein the information comprises anindication of a color the lighting load is configured to produce;displaying by the at least one processor on a display screen a graphicaluser interface that comprises an on-off actuator to turn the lightingload on and off; and displaying by the at least one processor togetherwith the on-off actuator in the graphical user interface a colorindicator that indicates the color the lighting load is configured toproduce.
 27. The non-transitory tangible computer readable medium ofclaim 25, wherein the instructions, when executed by the at least oneprocessor, further direct the at least one processor to: detect anactuation of the on-off actuator to turn the lighting load off; andresponsive to detecting the actuation of the on-off actuator to turn thelighting load off, remove from the graphical user interface the colorindicator.
 28. The non-transitory tangible computer readable medium ofclaim 25, wherein the instructions, when executed by the at least oneprocessor, further direct the at least one processor to: display withinthe graphical user interface a dimming actuator to change an intensitylevel of the lighting load; detect an actuation of the dimming actuatorto change the lighting load to a new intensity level; and responsive todetecting the actuation of the dimming actuator to change the lightingload to the new intensity level, communicate a message to the controllerto control the lighting load to the new intensity level.
 29. Thenon-transitory tangible computer readable medium of claim 28, whereinthe instructions, when executed by the at least one processor, furtherdirect the at least one processor to: display within the graphical userinterface a pallet together with the dimming actuator, wherein thepallet enable selection of a color; detect a selected color on thepallet; and responsive to detecting the selected color on the pallet,communicate a message to the controller to control the lighting load tothe selected color.
 30. The non-transitory tangible computer readablemedium of claim 29, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to:display within the graphical user interface the color indicator togetherwith the dimming actuator and the pallet; and responsive to detectingthe selected color on the pallet, change the color indicator to indicatethe selected color.
 31. The non-transitory tangible computer readablemedium of claim 30, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to: priorto detecting the selected color on the pallet, display the colorindicator as having a first size in the graphical user interface;responsive to detecting the selected color on the pallet, increasewithin the graphical user interface a size of the color indicator to asecond size that is greater than the first size; and subsequent toincreasing the size of the indicator to the second size, decrease withinthe graphical user interface the size of the color indicator from thesecond size to the first size.
 32. The non-transitory tangible computerreadable medium of claim 29, wherein the lighting load comprises aplurality of light emitting diodes (LEDs) including a white or asubstantially white LED; and wherein the instructions, when executed bythe at least one processor, further direct the at least one processorto: display a vibrancy actuator; detect an actuation of the vibrancyactuator; and responsive to detecting the actuation of the vibrancyactuator, communicate a message to the controller to control thelighting load to reduce an intensity of the white or the substantiallywhite LED while continuing to produce the color the lighting load isconfigured to produce.
 33. The non-transitory tangible computer readablemedium of claim 29, wherein the lighting load comprises a plurality oflight emitting diodes (LEDs) of a plurality of different colors; andwherein the pallet enables selection of a color only along a black bodycurve or enables selection of a color within color gamut formed by theplurality of different colored LEDs.
 34. The non-transitory tangiblecomputer readable medium of claim 25, wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: display within the graphical user interface a dimmingactuator to change an intensity of the lighting load, a warm-coolactuator to configure the lighting load to produce a color on a blackbody curve, and a full-color actuator to configure the lighting load toproduce a color within a color gamut comprising additional colors notfound on the black body curve.
 35. The non-transitory tangible computerreadable medium of claim 34, wherein the instructions, when executed bythe at least one processor, further direct the at least one processorto: detect an actuation of the warm-cool actuator; responsive todetecting the actuation of the warm-cool actuator, display on thedisplay screen a pallet together with the dimming actuator, wherein thepallet enables selection of a color on the black body curve; detect aselected color on the pallet; and responsive to detecting the selectedcolor on the pallet, communicate a message to the controller to controlthe lighting load to the selected color.
 36. The non-transitory tangiblecomputer readable medium of claim 35, wherein the instructions, whenexecuted by the at least one processor, further direct the at least oneprocessor to: prior to detecting the selected color on the pallet,display in the graphical user interface the color indicator asindicating a first color and having a first size; and responsive todetecting the selected color on the pallet, change within the graphicaluser interface the color indicator from indicating the first color toindicate the selected color, and increase within the graphical userinterface a size of the color indicator to a second size that is greaterthan the first size.
 37. The non-transitory tangible computer readablemedium of claim 34, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to:detect an actuation of the full-color actuator; responsive to detectingthe actuation of the full-color actuator, display on the display screena pallet together with the dimming actuator, wherein the pallet enablesselection of a color on the color gamut; detect a selected color on thepallet; and responsive to detecting the selected color on the pallet,communicate a message to the controller to control the lighting load tothe selected color.
 38. The non-transitory tangible computer readablemedium of claim 37, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to: priorto detecting the selected color on the pallet, display in the graphicaluser interface the color indicator as indicating a first color andhaving a first size; and responsive to detecting the selected color onthe pallet, change within the graphical user interface the colorindicator from indicating first color to indicate the selected color,and increase within the graphical user interface a size of the colorindicator to a second size that is greater than the first size.
 39. Thenon-transitory tangible computer readable medium of claim 34, whereinthe lighting load comprises a plurality of light emitting diodes (LEDs);and wherein the instructions, when executed by the at least oneprocessor, further direct the at least one processor to: display avibrancy actuator together with the dimming actuator, the warm-coolactuator, and the full-color actuator; detect an actuation of thevibrancy actuator; and responsive to detecting the actuation of thevibrancy actuator, communicate a message to the controller to controlthe lighting load to reduce an intensity of at least one of theplurality of LEDs while continuing to produce the color the lightingload is configured to produce.
 40. The non-transitory tangible computerreadable medium of claim 25, wherein the instructions, when executed bythe at least one processor, further direct the at least one processorto: display within the graphical user interface a pallet together withthe color indicator, wherein the pallet enables selection of a color;detect a selected color on the pallet; and responsive to detecting theselected color on the pallet: communicate a message to the controller tocontrol the lighting load to the selected color; and change within thegraphical user interface the color indicator to indicate the selectedcolor.
 41. The non-transitory tangible computer readable medium of claim40, wherein the instructions, when executed by the at least oneprocessor, further direct the at least one processor to: display withinthe graphical user interface an auto actuator that, when enabled, causesthe lighting load to produce light at a color rendering index (CRI)value that is greater than or equal to a CRI value threshold; anddetermine that the auto actuator is enabled; and wherein to communicatethe message to the controller to control the lighting load to theselected color comprises to communicate the message to the controller tocontrol the lighting load to the selected color and to further controlthe lighting load, based on the auto actuator being enabled, to a colorrendering index (CRI) value that is greater than or equal to the CRIvalue threshold.
 42. The non-transitory tangible computer readablemedium of claim 41, wherein the instructions, when executed by the atleast one processor, further direct the at least one processor to:determine that the auto actuator is disabled; responsive to determiningthat the auto actuator is disabled, display within the graphical userinterface a vibrancy actuator to change a vibrancy level of the lightingload; detect an actuation of the vibrancy actuator to change thelighting load to a new vibrancy level; and responsive to detecting theactuation of the vibrancy actuator to change the lighting load to thenew vibrancy level, communicate a message to the controller to controlthe lighting load to the new vibrancy level.
 43. The method of claim 26,further comprising: detecting by the at least one processor an actuationof the on-off actuator to turn the lighting load off; and responsive todetecting the actuation of the on-off actuator to turn the lighting loadoff, removing by the at least one processor from the graphical userinterface the color indicator.
 44. The method of claim 26, furthercomprising: displaying by the at least one processor within thegraphical user interface a dimming actuator to change an intensity levelof the lighting load; detecting by the at least one processor anactuation of the dimming actuator to change the lighting load to a newintensity level; and responsive to detecting the actuation of thedimming actuator to change the lighting load to the new intensity level,communicating by the at least one processor a message to the controllerto control the lighting load to the new intensity level.
 45. The methodof claim 44, further comprising: displaying by the at least oneprocessor within the graphical user interface a pallet together with thedimming actuator, wherein the pallet enable selection of a color;detecting by the at least one processor a selected color on the pallet;and responsive to detecting the selected color on the pallet,communicating by the at least one processor a message to the controllerto control the lighting load to the selected color.
 46. The method ofclaim 45, further comprising: displaying by the at least one processorwithin the graphical user interface the color indicator together withthe dimming actuator and the pallet; and responsive to detecting theselected color on the pallet, changing by the at least one processor thecolor indicator to indicate the selected color.
 47. The method of claim45, wherein the lighting load comprises a plurality of light emittingdiodes (LEDs) including a white or a substantially white LED; andwherein the method further comprises: displaying by the at least oneprocessor a vibrancy actuator; detecting by the at least one processoran actuation of the vibrancy actuator; and responsive to detecting theactuation of the vibrancy actuator, communicating by the at least oneprocessor a message to the controller to control the lighting load toreduce an intensity of the white or the substantially white LED whilecontinuing to produce the color the lighting load is configured toproduce.
 48. The method of claim 45, wherein the lighting load comprisesa plurality of light emitting diodes (LEDs) of a plurality of differentcolors; and wherein the pallet enables selection of a color only along ablack body curve or enables selection of a color within color gamutformed by the plurality of different colored LEDs.
 49. The method ofclaim 26, further comprising: displaying by the at least one processorwithin the graphical user interface a dimming actuator to change anintensity of the lighting load, a warm-cool actuator to configure thelighting load to produce a color on a black body curve, and a full-coloractuator to configure the lighting load to produce a color within acolor gamut comprising additional colors not found on the black bodycurve.
 50. The method of claim 49, further comprising: detecting by theat least one processor an actuation of the warm-cool actuator;responsive to detecting the actuation of the warm-cool actuator,displaying by the at least one processor on the display screen a pallettogether with the dimming actuator, wherein the pallet enables selectionof a color on the black body curve; detecting by the at least oneprocessor a selected color on the pallet; and responsive to detectingthe selected color on the pallet, communicating by the at least oneprocessor a message to the controller to control the lighting load tothe selected color.
 51. The method of claim 49, further comprising:detecting by the at least one processor an actuation of the full-coloractuator; responsive to detecting the actuation of the full-coloractuator, displaying by the at least one processor on the display screena pallet together with the dimming actuator, wherein the pallet enablesselection of a color on the color gamut; detecting by the at least oneprocessor a selected color on the pallet; and responsive to detectingthe selected color on the pallet, communicating by the at least oneprocessor a message to the controller to control the lighting load tothe selected color.
 52. The method of claim 49, wherein the lightingload comprises a plurality of light emitting diodes (LEDs); and whereinthe method further comprises: displaying by the at least one processor avibrancy actuator together with the dimming actuator, the warm-coolactuator, and the full-color actuator; detecting by the at least oneprocessor an actuation of the vibrancy actuator; and responsive todetecting the actuation of the vibrancy actuator, communicating by theat least one processor a message to the controller to control thelighting load to reduce an intensity of at least one of the plurality ofLEDs while continuing to produce the color the lighting load isconfigured to produce.
 53. The method of claim 26, further comprising:displaying by the at least one processor within the graphical userinterface a pallet together with the color indicator, wherein the palletenables selection of a color; detecting by the at least one processor aselected color on the pallet; and responsive to detecting the selectedcolor on the pallet: communicating by the at least one processor amessage to the controller to control the lighting load to the selectedcolor; and changing by the at least one processor within the graphicaluser interface the color indicator to indicate the selected color. 54.The method of claim 53, further comprising: displaying by the at leastone processor within the graphical user interface an auto actuator that,when enabled, causes the lighting load to produce light at a colorrendering index (CRI) value that is greater than or equal to a CRI valuethreshold; and determining by the at least one processor that the autoactuator is enabled; and wherein communicating the message to thecontroller to control the lighting load to the selected color comprisescommunicating the message to the controller to control the lighting loadto the selected color and to further control the lighting load, based onthe auto actuator being enabled, to a color rendering index (CRI) valuethat is greater than or equal to the CRI value threshold.
 55. The methodof claim 54, further comprising: determining by the at least oneprocessor that the auto actuator is disabled; responsive to determiningthat the auto actuator is disabled, displaying by the at least oneprocessor within the graphical user interface a vibrancy actuator tochange a vibrancy level of the lighting load; detecting by the at leastone processor an actuation of the vibrancy actuator to change thelighting load to a new vibrancy level; and responsive to detecting theactuation of the vibrancy actuator to change the lighting load to thenew vibrancy level, communicating by the at least one processor amessage to the controller to control the lighting load to the newvibrancy level.